inkscape closes due to "internal error"

[Quartz]

I am using Fedora 9, and the Bug Buddy conveniently gathered the attached info. I have been suffering from what I believe is this same bug for a long while now, and only now have I caught it with Bug Buddy like this.

This is a very difficult, evasive bug. The steps to reproduce it are sorrowfully vague, but here they are:

1. Create a large, complicated SVG image that takes a long time to render.
 A. Try gaussian blur.
 B. Try different blend modes in many layers.
 C. Maybe even importing large bitmaps.
2. Make inkscape begin rendering something of it.
 A. Either export the image, or ...
 B. Draw a path with a great number of nodes.*
3. While it's rendering (or immediately after it's exported) while it's still busy, press some buttons or some keys to give it another task.
 A. If I've just drawn a path, I'll usually lower it to the bottom, or down one or two drawing elements.
 B. With these two crashes Bug Buddy caught, I had closed the export window and told it to save the document, then closed inkscape.
4. Boom.

* This has been the method by which I have seen the grand majority of the crashes, although unfortunately for both of the crashes Bug Buddy caught this time I had just finished an export instead.

Sometimes it shows me a filename for an emergency backup, sometimes it'll tell me the backup failed. With these two particular crashes Bug Buddy caught it said nothing whatsoever about emergency backups, except in the standard error output seen in the logs (as usual) that Bug Buddy provided. (Incidently, it says in the logs that the emergency save succeeded, but I can't find any save files in its usual places.)

I'm afraid that Bud Buddy has caught a different error this time than the one that's been plaguing me all along. With your confirmation I might submit a separate bug report if Bug Buddy ever catches my more usual error.

[Pablo Trabajos (pajarico)]

Could you please try this bug with a newer release of Inkscape (currently 0.47-pre1)?

[Alex Valavanis (valavanisalex)]

A request for more information has been pending for a long time, and the developers don't have enough information to fix the bug at the moment. I'll close this report for the moment, but feel free to reopen it if anyone can provide the requested information.

[uellue (dieter-uellue)]

I've had a similar problem with 0.48.4 r9939 on Windows 7 Enterprise 64 bit.

I've created a LOT of tiled clones of a circle. Then I've turned the clones into individual objects and combined them. After that step there were drawing errors. Some random circles were drawn as filled. The circles drawn as filled changed depending on the zoom level. I saved the file at that point, it is appended. Inkscape crashed when I tried to export a bitmap.

When I opened the file again, the drawing errors persisted. Inkscape didn't crash when I exported a bitmap the first time. It just included the drawing error in the exported bitmap. This bitmap with drawing error is appended. When I exported a second time at higher resolution, Inkscape crashed again.

[su_v (suv-lp)]

Closing again (see comment 3) - the crash reported later in comments 4-5 for Inkscape 0.48.4 does not reproduce with 0.48.4 and 0.48.5 on OS X 10.7.5 (Inkscape 0.48.x requires increasing amounts of memory - close to 2GB here - when exporting the file repeatedly to bitmap at higher resolutions, which could cause Windows builds to crash (there are other reports tracking such memory-related crashes on Windows when exporting to bitmap)). The rendering errors (depending on zoom level and export resolution) are known issues with the old renderer tracked in other reports and fixed in the new cairo-based renderer in Inkscape >= 0.91).