Inkscape crashes on high level of zoom in

Bug #1124207 reported by Duarte Ramos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
High
jazzynico
Inkscape Devlibs
Fix Released
High
jazzynico

Bug Description

I'm on Inkscape 0.49 nightly inkscape_r12119-201302120630, previous nightlies exibited the same crash, either on Windows XP 64bits or Windows 7 64 Bits.

On a specific file with a lot of duplicate clone objects with a gradient fill, at high zoom levels Inkscape crashes and an error window appears.

In windows 7 the error window is blank and unreadable, but the error report says it's the Cairo Rendering Engine specifically the libcairo-2.dll file.

File provided in attachement, to recreate just zoom in progressively and it will eventually crash, seems to get aggravated with larger window sizes hence larger rendered area.

Revision history for this message
Duarte Ramos (duarte-framos) wrote :
su_v (suv-lp)
tags: added: cairo win32
removed: libcairo-2.dll renderer
Changed in inkscape:
importance: Undecided → High
Revision history for this message
su_v (suv-lp) wrote :

Crash not reproduced with
- 32bit builds on Mac OS X 10.5.8 (OpenMP enabled)
  (GTK+/X11 2.24.8, cairo 1.10.2), (GTK+/Quartz 2.24.10, cairo 1.11.4)
- 64bit builds on OS X 10.7.4 (OpenMP enabled)
  (GTK+/X11 2.24.10, cairo 1.12.2), (GTK+/Quartz 2.24.15, cairo 1.12.14)

> seems to get aggravated with larger window sizes hence larger
> rendered area.

Possibly this observation is limiting the usefulness of my tests: available screen sizes are limited to 15.4" and 13" (both systems are MBPs without external monitor). I do notice that trunk temporarily consumes huge amounts of memory when zooming in closer (compared to stable) - it is released immediately when zooming back out to page size or further. This memory usage can quickly grow to 1.4 - 1.6 GB real memory, and then revert back to < 300 MB (after zooming back out).

Revision history for this message
Duarte Ramos (duarte-framos) wrote :

Thanks for the quick response.
Tested again with the same mentioned version inkscape_r12119-201302120630 but now at home on my Windows 7 64 bits machine with 16Gb of Ram (unlikely to be a lack of memory problem) and came to the conclusion that it is definitely related to window size, or viewable rendered viewport area.

I have two Dell monitors each at 2560x1600, I can zoom in without crash with a small window size, or if the window not maximized (smaller viewable area) if afterwards I maximize the window with the drawing already zoomed in Inkscape still behaves, but if I start panning around some screen tearing starts to happen in viewport, and black or white stripes start to appear as if rendering is failing partially, before the actual crash occurs.
I also noticed that even though this Inkscape version feels generally snappier and faster to render than 1.48.4, this particular file at high zoom levels seems quite sluggish when compared.

Attached screenshot shows two Inkscape windows opened with the same file originally attached to the bug report, one is not maximizes and handles the file with larger zoom level without much trouble, the one on the background has crashed, with the black Window (Which sometimes will show something like "The application as encountered an error and will now close"), the windows crash report, and the failed render (all the white areas) and some screen tearing, like missing patches of drawing

Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced on Windows XP, Inkscape trunk revision 12119 official devlibs (cairo 1.11.2, cairomm 1.10.0).
I confirm it doesn't crash with a small window, but only if it's maximized or large enough.
No bt, but I get the following message (from Cairo) just before Inkscape hangs:

_create_dc_and_bitmap: OpÚration rÚussie.

Not reproduced with the experimental cross-compiled devlibs from OpenSuse (cairo 1.10.2, cairomm 1.10.0).

Changed in inkscape:
status: New → Triaged
jazzynico (jazzynico)
Changed in inkscape-devlibs:
status: New → Triaged
Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced again on Windows XP, Inkscape trunk revision 12275 and devlibs r46 (Cairo 1.12.14).

Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced with Inkscape trunk rev. 14862, Cairo (1.14.6) and Pixman (0.34.0) from the official win32 devlibs (updated rev. 61).

Changed in inkscape-devlibs:
assignee: nobody → jazzynico (jazzynico)
importance: Undecided → High
status: Triaged → Fix Released
Changed in inkscape:
assignee: nobody → jazzynico (jazzynico)
milestone: none → 0.91.1
status: Triaged → Fix Committed
jazzynico (jazzynico)
Changed in inkscape:
milestone: 0.91.1 → 0.92
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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