Bug 784721

Summary: 8000x8000 image from http://www.flickr.com/photos/gsfc/6760135001/sizes/o/in/photostream/ crashes X
Product: [Fedora] Fedora Reporter: Diego Calleja <diegocg>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: ajax, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-24 00:01:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
X.org log with backtrace none

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.