Help/advice needed with crash on bitmap paste/import (embed) on OS X >= 10.9
Current 0.91.x and trunk packages for OS X are affected by a rather critical issue on OS X 10.9 Mavericks and 10.10 Yosemite:
* Pasting a bitmap image from the clipboard, or importing it via 'File > Import' with default import options (embed, resolution from file) crashes the application. [1]
* Oddly, it seems that if the build has debug messages (to stdout) in the source code related to retrieving the image resolution from file, the crash no longer happens.[2]
* First observed by testers of experimental osxmenu builds back in Nov 2013 (osxmenu is always quite up-to-date with trunk at any time). The debug messages had been committed in the osxmenu branch and I haven't seen new feedback about the same type of crashes with osxmenu builds. [3]
* One tester of 0.91 pre-release and trunk snapshot builds reported OTOH that this type of crashes stopped after rebooting and switching to a different user (same system otherwise) - see comment 10 in bug 1398521 ([1]).
* The crashes never reproduced for me on OS X 10.7.5 (build system for current available packages).
How to proceed?
This crash occurs in a very basic feature, and can get easily disruptive for Inkscape users on current OS X. Should we ship the upcoming stable release package with the debug messages applied as part of packaging (maintaining the diff in 'packaging/macosx')?
Regards, V
[1] Related bug reports: https://bugs.launchpad.net/bugs/1398521 https://bugs.launchpad.net/bugs/1410793 https://bugs.launchpad.net/bugs/1413478
[2] Diff applied to custom test builds (reportedly don't crash): https://bugs.launchpad.net/inkscape/+bug/1410793/comments/7 https://www.dropbox.com/sh/magg5vw5j3y1y3u/AADgl_FtaO2ZLKAVOOgO2EsMa/Inkscap...
[3] Backtrace of debug build by an early tester of osxmenu (at the time on Mavericks) - Nov 22, 2013: https://gist.github.com/su-v/cd4ef1cc1c4832f07989 I noticed 'val=NaN' on this line: https://gist.github.com/su-v/cd4ef1cc1c4832f07989#file-crash-mavericks-impor...
On 22-Jan-2015 07:00, su_v wrote:
- Oddly, it seems that if the build has debug messages (to stdout) in
the source code related to retrieving the image resolution from file, the crash no longer happens.[2]
That is a classic symptom of a memory access violation - include a bit of extra code and bugs mysteriously disappear.
How to proceed?
I don't have a Mac so cannot help with this, but somebody needs to run that binary in gdb, trigger the crash, and then do a bt. It is usually evident from examining the code at the crash location where the memory access problem is. If valgrind works on OS X that would help too. (But I don't think it does.)
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech
On 2015-01-22 19:40 (+0100), mathog wrote:
I don't have a Mac so cannot help with this, but somebody needs to run that binary in gdb, trigger the crash, and then do a bt. It is usually evident from examining the code at the crash location where the memory access problem is. If valgrind works on OS X that would help too. (But I don't think it does.)
1) see original mail:
On 2015-01-22 16:00 (+0100), su_v wrote:
- First observed by testers of experimental osxmenu builds back in Nov
2013 (osxmenu is always quite up-to-date with trunk at any time). The debug messages had been committed in the osxmenu branch and I haven't seen new feedback about the same type of crashes with osxmenu builds. [3]
[3] Backtrace of debug build by an early tester of osxmenu (at the time on Mavericks) - Nov 22, 2013: https://gist.github.com/su-v/cd4ef1cc1c4832f07989 I noticed 'val=NaN' on this line: https://gist.github.com/su-v/cd4ef1cc1c4832f07989#file-crash-mavericks-impor...
2) I have uploaded a new debug build (compiled with '-g -O0', but without the debug messages diff applied) [1]: 'Inkscape-0.91+devel-r13867-2-x11-10.7-x86_64-debug.dmg' at https://www.dropbox.com/sh/2n7aim2wcrn6l3h/AADjQQ_484Z_Po1X3RSqa29na?dl=0
Anyone with Xcode installed can run the packaged app interactively via debugger in the Terminal: $ INK_DEBUG=gdb /Applications/Inkscape.app/Contents/MacOS/Inkscape or (newer Xcode only include lldb): $ INK_DEBUG=lldb /Applications/Inkscape.app/Contents/MacOS/Inkscape
Regards, V
[1] debug build does not include tutorials or translations, to reduce download size.
I tried to import (copy-paste from clipboard didn't work for me) and my build crashed on me. :(
On Fri, Jan 23, 2015 at 3:04 AM, su_v <suv-sf@...58...> wrote:
On 2015-01-22 19:40 (+0100), mathog wrote:
I don't have a Mac so cannot help with this, but somebody needs to run that binary in gdb, trigger the crash, and then do a bt. It is usually evident from examining the code at the crash location where the memory access problem is. If valgrind works on OS X that would help too. (But I don't think it does.)
- see original mail:
On 2015-01-22 16:00 (+0100), su_v wrote:
- First observed by testers of experimental osxmenu builds back in Nov
2013 (osxmenu is always quite up-to-date with trunk at any time). The debug messages had been committed in the osxmenu branch and I haven't seen new feedback about the same type of crashes with osxmenu builds. [3]
[3] Backtrace of debug build by an early tester of osxmenu (at the time on Mavericks) - Nov 22, 2013: https://gist.github.com/su-v/cd4ef1cc1c4832f07989 I noticed 'val=NaN' on this line: https://gist.github.com/su-v/cd4ef1cc1c4832f07989#file-crash-mavericks-impor...
- I have uploaded a new debug build (compiled with '-g -O0', but
without the debug messages diff applied) [1]: 'Inkscape-0.91+devel-r13867-2-x11-10.7-x86_64-debug.dmg' at https://www.dropbox.com/sh/2n7aim2wcrn6l3h/AADjQQ_484Z_Po1X3RSqa29na?dl=0
Anyone with Xcode installed can run the packaged app interactively via debugger in the Terminal: $ INK_DEBUG=gdb /Applications/Inkscape.app/Contents/MacOS/Inkscape or (newer Xcode only include lldb): $ INK_DEBUG=lldb /Applications/Inkscape.app/Contents/MacOS/Inkscape
Regards, V
[1] debug build does not include tutorials or translations, to reduce download size.
New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 2015-01-23 12:47 (+0100), Partha Bagchi wrote:
I tried to import (copy-paste from clipboard didn't work for me) and my build crashed on me. :(
Thanks for trying ...
1) "my build" refers to your experimental custom GTK3/Quartz build or to a regular GTK2/X11 build?
2) If Quartz backend, GTK2 or GTK3: Support of data exchange via the native clipboard is broken upstream in the quartz backend of the toolkit [1]. You can copy & paste bitmap images between GIMP and Inkscape though, assuming both are compiled with the GTK+/Quartz backend, or drag&drop a bitmap image from the Finder onto the Inkscape canvas.
3) If Quartz backend, GTK3: I didn't attempt to launch your package on my system, but had feedback by another user that it crashed as soon as any file chooser dialog was opened ('File > Open', 'File > Import' or 'File > Save/Save as'). This would be a different crash, limited to your custom GTK3 package and not related to the crash I'm asking about in this thread. Since you neither provided details nor a backtrace, I can't really tell what the crash you experienced is about.
Regards, V
[1] https://bugs.launchpad.net/inkscape/+bug/546934 https://bugzilla.gnome.org/show_bug.cgi?id=692123
On Fri, Jan 23, 2015 at 3:04 AM, su_v <...> wrote:
On 2015-01-22 19:40 (+0100), mathog wrote:
I don't have a Mac so cannot help with this, but somebody needs to run that binary in gdb, trigger the crash, and then do a bt. It is usually evident from examining the code at the crash location where the memory access problem is. If valgrind works on OS X that would help too. (But I don't think it does.)
- see original mail:
On 2015-01-22 16:00 (+0100), su_v wrote:
- First observed by testers of experimental osxmenu builds back in Nov
2013 (osxmenu is always quite up-to-date with trunk at any time). The debug messages had been committed in the osxmenu branch and I haven't seen new feedback about the same type of crashes with osxmenu builds. [3]
[3] Backtrace of debug build by an early tester of osxmenu (at the time on Mavericks) - Nov 22, 2013: https://gist.github.com/su-v/cd4ef1cc1c4832f07989 I noticed 'val=NaN' on this line: https://gist.github.com/su-v/cd4ef1cc1c4832f07989#file-crash-mavericks-impor...
- I have uploaded a new debug build (compiled with '-g -O0', but
without the debug messages diff applied) [1]: 'Inkscape-0.91+devel-r13867-2-x11-10.7-x86_64-debug.dmg' at https://www.dropbox.com/sh/2n7aim2wcrn6l3h/AADjQQ_484Z_Po1X3RSqa29na?dl=0
Anyone with Xcode installed can run the packaged app interactively via debugger in the Terminal: $ INK_DEBUG=gdb /Applications/Inkscape.app/Contents/MacOS/Inkscape or (newer Xcode only include lldb): $ INK_DEBUG=lldb /Applications/Inkscape.app/Contents/MacOS/Inkscape
Regards, V
[1] debug build does not include tutorials or translations, to reduce download size.
New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, Jan 23, 2015 at 8:04 AM, su_v <suv-sf@...58...> wrote:
On 2015-01-23 12:47 (+0100), Partha Bagchi wrote:
I tried to import (copy-paste from clipboard didn't work for me) and my build crashed on me. :(
Thanks for trying ...
You are welcome ...
- "my build" refers to your experimental custom GTK3/Quartz build or to
a regular GTK2/X11 build?
Experimental GTK3 build - Sorry thought it was obvious.
- If Quartz backend, GTK2 or GTK3:
Support of data exchange via the native clipboard is broken upstream in the quartz backend of the toolkit [1]. You can copy & paste bitmap images between GIMP and Inkscape though, assuming both are compiled with the GTK+/Quartz backend, or drag&drop a bitmap image from the Finder onto the Inkscape canvas.
- If Quartz backend, GTK3:
I didn't attempt to launch your package on my system, but had feedback by another user that it crashed as soon as any file chooser dialog was opened ('File > Open', 'File > Import' or 'File > Save/Save as'). This would be a different crash, limited to your custom GTK3 package and not related to the crash I'm asking about in this thread. Since you neither provided details nor a backtrace, I can't really tell what the crash you experienced is about.
Yes, this is a result of a lack of schemas on OSX. Once I installed gsettings-desktop-schemas-3.14.5, it works fine. Maybe you can try installing them and see if the crash goes away? It did for me.
And yes, copy/paste from clipboard does not work.
Regards, V
Thanks, Partha
On 2015-01-24 19:48 (+0100), Partha Bagchi wrote:
On Fri, Jan 23, 2015 at 8:04 AM, su_v <suv-sf@...58...> wrote:
On 2015-01-23 12:47 (+0100), Partha Bagchi wrote:
I tried to import (copy-paste from clipboard didn't work for me) and my build crashed on me. :(
Thanks for trying ...
You are welcome ...
- "my build" refers to your experimental custom GTK3/Quartz build or to
a regular GTK2/X11 build?
Experimental GTK3 build - Sorry thought it was obvious.
I can't mind-read emails, sorry, and I try not to make assumptions (especially if it's about technical data, where a few words (e.g. osxmenu branch r12895, experimental GTK3/Quartz 3.14.7, compiled with custom GCC 4.x on OS X 10.10, custom packaging) would have been sufficient to communicate the facts).
If the mentioned build is based on the osxmenu branch (is it? See, I'm still forced to make assumptions about facts ;-) ), then the crash as reported very likely doesn't reproduce anyway, as described in my first mail - the osxmenu branch has those debug messages which apparently may prevent that the crash occurs included (since April 2014).
- If Quartz backend, GTK3:
I didn't attempt to launch your package on my system, but had feedback by another user that it crashed as soon as any file chooser dialog was opened ('File > Open', 'File > Import' or 'File > Save/Save as'). This would be a different crash, limited to your custom GTK3 package and not related to the crash I'm asking about in this thread. Since you neither provided details nor a backtrace, I can't really tell what the crash you experienced is about.
Yes, this is a result of a lack of schemas on OSX. Once I installed gsettings-desktop-schemas-3.14.5, it works fine. Maybe you can try installing them and see if the crash goes away? It did for me.
In this case, AFAICT the crash you experienced with the custom experimental GTK3/Quartz (osxmenu-based) package is not related to the one discussed in this thread (crash on embedding of imported or pasted images, with unmodified 091pre3, 091pre4 and 0.91+devel builds, using GTK+ 2.24 with X11 backend).
Thanks again for testing, V
On Sat, Jan 24, 2015 at 2:55 PM, su_v <suv-sf@...58...> wrote:
On 2015-01-24 19:48 (+0100), Partha Bagchi wrote:
On Fri, Jan 23, 2015 at 8:04 AM, su_v <suv-sf@...58...> wrote:
On 2015-01-23 12:47 (+0100), Partha Bagchi wrote:
I tried to import (copy-paste from clipboard didn't work for me) and my build crashed on me. :(
Thanks for trying ...
You are welcome ...
- "my build" refers to your experimental custom GTK3/Quartz build or to
a regular GTK2/X11 build?
Experimental GTK3 build - Sorry thought it was obvious.
I can't mind-read emails, sorry, and I try not to make assumptions (especially if it's about technical data, where a few words (e.g. osxmenu branch r12895, experimental GTK3/Quartz 3.14.7, compiled with custom GCC 4.x on OS X 10.10, custom packaging) would have been sufficient to communicate the facts).
If the mentioned build is based on the osxmenu branch (is it? See, I'm still forced to make assumptions about facts ;-) ), then the crash as reported very likely doesn't reproduce anyway, as described in my first mail - the osxmenu branch has those debug messages which apparently may prevent that the crash occurs included (since April 2014).
- If Quartz backend, GTK3:
I didn't attempt to launch your package on my system, but had feedback by another user that it crashed as soon as any file chooser dialog was opened ('File > Open', 'File > Import' or 'File > Save/Save as'). This would be a different crash, limited to your custom GTK3 package and not related to the crash I'm asking about in this thread. Since you neither provided details nor a backtrace, I can't really tell what the crash you experienced is about.
Yes, this is a result of a lack of schemas on OSX. Once I installed gsettings-desktop-schemas-3.14.5, it works fine. Maybe you can try installing them and see if the crash goes away? It did for me.
In this case, AFAICT the crash you experienced with the custom experimental GTK3/Quartz (osxmenu-based) package is not related to the one discussed in this thread (crash on embedding of imported or pasted images, with unmodified 091pre3, 091pre4 and 0.91+devel builds, using GTK+ 2.24 with X11 backend).
OK, sounds good. I wanted to report that I am not experiencing any more crashes on embedding of imported images using GTK+ 3.14.x with Quartz backend.
Thanks again for testing, V
participants (3)
-
mathog -
Partha Bagchi -
su_v