GNOME Bugzilla – Bug 644335
SEGV while scrolling over large SVG (attached) using eog 2.30.0-0ubuntu1
Last modified: 2011-03-10 18:29:54 UTC
I'm using ubuntu lucid lynx (10.04) which means I got eog "2.30.0-0ubuntu1". I was playing around with generated SVG graphs showing the #includes in firefox when suddenly eog crashed. I think it's because the SVG happened to get really wide. repro: 1. load SVG file 2. zoom a lot 3. scroll all the way to the left and then all the way to the right Here is the backtrace for the SEGV: data=0x43d480) at /build/buildd/gtk+2.0-2.20.1/gtk/gtkmarshalers.c:84
+ Trace 226254
Created attachment 183019 [details] wide SVG file that caused the SEGV
better repro steps: 1. click the ZOOM button on the toolbar 7 times to make the zoom level 100% 2. double click the eog window caption bar to maximize its window 3. scroll all the way to the left and then all the way to the right These steps hit the crash 100% of the time for me. It also works if I switch the order of steps 2 and 3. My screen res, should be relevant, is 1680x1050.
Yes, there's likely two problems involved here. First, you are right about the size. eog has problems drawing larger raster images (bug 163090). The limit is ~32k px in any direction. For 100% zoom we also used a rasterized variant of displayed SVGs in 2.32. The current development series 2.91.x (the upcoming 3.0) also renders natively at 100% so this not a limitation anymore. Second, 2.32.0 had a known regression regarding on how far it let you scroll your image (bug 631710). Precisely it would let you scroll too far by not setting the adjustment values of the scrollbars correctly, rendering garbage once you scrolled out of the image area. This apparently even causes a crash in the rendering code with your image. Yet, this has been fixed in 2.32.1 where I cannot reproduce this anymore while I can reproduce it with 2.32.0. --- Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 631710 ***