Bug 63396 - Xorg crashes in radeon_get_pixmap_bo on exporting graph at 1200 dpi in Mathematica
Summary: Xorg crashes in radeon_get_pixmap_bo on exporting graph at 1200 dpi in Mathem...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/r300 (show other bugs)
Version: 9.1
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-10 19:23 UTC by auxsvr
Modified: 2013-04-15 14:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Full backtrace (5.93 KB, text/plain)
2013-04-10 19:23 UTC, auxsvr
Details
Xorg.log (35.21 KB, text/plain)
2013-04-10 19:26 UTC, auxsvr
Details

Description auxsvr 2013-04-10 19:23:18 UTC
Created attachment 77765 [details]
Full backtrace

If I attempt to export a graph in Mathematica with high resolution (1200 dpi), then Xorg crashes reliably. The graphics card is a radeon 9600XT.

Mesa-9.1.1
xorg-x11-server-7.6_1.13.2
xf86-video-ati-7.0.0-2.1.1
libdrm2-2.4.43
linux 3.7.10
Comment 1 auxsvr 2013-04-10 19:26:14 UTC
Created attachment 77766 [details]
Xorg.log
Comment 2 auxsvr 2013-04-10 19:28:16 UTC
There might be some connection, other than the way of triggering, with bug 63393.
Comment 3 Michel Dänzer 2013-04-12 14:44:15 UTC
Does this still happen with xf86-video-ati 7.1? I think Git commit 53af6aa99dfb67b5223c28d5129a79694165048d might have fixed it.

Note that this probably happens because there is not enough graphics memory for the high resolution graph, the best we can do is fail more gracefully.
Comment 4 auxsvr 2013-04-12 16:01:35 UTC
xf86-ati-7.1 fixes this, I apologize for wasting your time. Xorg uses about 1GB RAM, then returns to normal, and the image is exported as expected.
Comment 5 Michel Dänzer 2013-04-15 14:14:21 UTC
Resolving per comment #4 (BTW, you can do this yourself :), thanks for verifying.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.