Bug 784721 - 8000x8000 image from http://www.flickr.com/photos/gsfc/6760135001/sizes/o/in/photostream/ crashes X
Summary: 8000x8000 image from http://www.flickr.com/photos/gsfc/6760135001/sizes/o/in/...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 22:29 UTC by Diego Calleja
Modified: 2012-05-24 00:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-24 00:01:27 UTC
Type: ---


Attachments (Terms of Use)
X.org log with backtrace (43.98 KB, text/plain)
2012-01-25 22:29 UTC, Diego Calleja
no flags Details

Description Diego Calleja 2012-01-25 22:29:16 UTC
Created attachment 557545 [details]
X.org log with backtrace

Description of problem:

While doing some critical research in reddit.com/r/pics, this 8000x8000 image crashed my X: http://www.flickr.com/photos/gsfc/6760135001/sizes/o/in/photostream/

The browser was Firefox and the desktop is using composited kwin via opengl.

Version-Release number of selected component (if applicable):

Standard F16 packages

Hardware: Sandybridge Intel(R) Core(TM) i7-2600K

How reproducible:

Almost always: I've got it to load it somehow one time, but celaning the caches and reloading the image made it crash again. I also was unable to reproduce it under openbox

  
Additional info:
I've got a backtrace (included), but I wasn't able to make sense of it. I even installed the debuginfo package for the driver, but the backtrace didn't improve.

Comment 1 Adam Jackson 2012-05-23 19:53:27 UTC
Can you reproduce this with current kernels from updates?  Images that large will cause some rather complicated software fallbacks, and there's been some fixes in that area recently.

Comment 2 Diego Calleja 2012-05-24 00:01:27 UTC
Nope, I can't. Also, it's *much* faster than it used to be. I'll close this.


Note You need to log in before you can comment on or make changes to this bug.