Inkscape

trunk: crash when reloading a file with linked color profile

Bug #1300959 reported by su_v
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned

Bug Description

Steps to reproduce (r13248, lcms1):
1) launch trunk r13248 (default prefs, new default doc)
2) open 'Document Properties > Color' and link a color profile to current doc
3) save file and close window
4) open just saved file from 'File > Open recent'

Steps to reproduce (r13248, lcms2):
1) launch trunk r13248 (default prefs, new doc)
2) save file (Shift+Ctrl+S)
3) open 'Document Properties > Color' and link a color profile to current doc
4) close window
4) open just saved file from 'File > Open recent'

Crash:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x0000000000000000
0x000000010071bc1f in Inkscape::XML::SignalObserver::set (this=0x1108a6510, o=0x140f759f0) at ../../src/xml/helper-observer.cpp:18
18 _oldsel->getRepr()->removeObserver(*this);

Reproduced with r13248 (lcms1, lcms2) on OS X 10.7.5.
Not reproduced with stable 0.48.4 and latest 0.48.x r10020.

See original description
Revision history for this message
su_v (suv-lp) wrote :
su_v (suv-lp)
tags: added: regression
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Crunchbang Waldorf, Inkscape trunk revision 13261, lcms2.
Not reproduced on Windows XP, Inkscape trunk revision 13249, lcms2.

~suv> launch patched trunk build...

Could you please confirm you can reproduce the crash with 13249 (which is actually the "patched" version of 13248).

su_v (suv-lp)
description: updated
description: updated
Revision history for this message
su_v (suv-lp) wrote :

> Could you please confirm you can reproduce the crash with
> 13249 (which is actually the "patched" version of 13248).

Confirmed with r13264 (GTK+/Quartz with lcms1 1.19, lcms2 2.5; GTK+/X11 with lcms 1.19, lcms2 2.6) - possibly it is a timing issue: the crash doesn't reproduce consistently (it seems that the faster I get through the steps the more likely the crash occurs).

Revision history for this message
su_v (suv-lp) wrote :

Also reproduced with r13264 on Ubuntu 13.10 (VM, 64bit) (backtrace attached).

jazzynico (jazzynico)
Changed in inkscape:
importance: Undecided → High
Revision history for this message
su_v (suv-lp) wrote :

Failed to reproduce based on the provided steps with latest trunk (r13631, lcms2) on OS X 10.7.5

Changed in inkscape:
milestone: 0.91 → none
status: New → Incomplete
Revision history for this message
su_v (suv-lp) wrote :

Closing for now - see last comment (no success in attempting to reproduce with later trunk build).

Changed in inkscape:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.