Bug 7484 - gnash open source flash player causes signal 11
Summary: gnash open source flash player causes signal 11
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.1 (2006.05)
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-10 10:41 UTC by Andrew Williams
Modified: 2007-02-22 14:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Andrew Williams 2006-07-10 10:41:45 UTC
I'm running an amd64 machine with the latest Gentoo Linux, 2006.0, with ~amd64
testing packages. Compiling and installing gnash causes the X server to abort
with the following error:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x90) [0x480240]
1: /lib/libc.so.6 [0x2b48271bc600]
2:
/usr/lib64/xorg/modules/extensions/libGLcore.so(_mesa_update_draw_buffer_bounds+0)
[0x2b48399f0cb0]

Fatal server error:
Caught signal 11.  Server aborting

This occurs not when going to a site with flash (most flash apps appear to work,
considering gnash's alpha status) but when *leaving*, ie going to another site.

I've informed the gnash mailing list and I'm not the only one with this problem.
My PC is running gcc 4.1.1 and doesn't have anything out of the ordinary on it.

As a test, I tried to install gnash on another machine, this one 32-bit Pentium
4, running a similar Gentoo setup. This also causes an identical crash , but
with a slightly different error message:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0xa3) [0x80c044d]

Fatal server error:
Caught signal 11.  Server aborting

Both machines are using different nvidia cards running the open source drivers.
Both have xorg-server 1.1.1 and mesa 6.5, although the crash has been occurring
for a couple of months, and through several xorg component upgrades, both with
the open source and binary nvidia drivers.

Other opengl apps run correctly, albeit slowly due to lack of direct rendering.
Comment 1 Fabio Pedretti 2006-07-17 06:44:52 UTC
Seems that gnash people have now fixed gnash so that it doesn't crash anymore.
However the bug is still reproducible with older version of gnash (e.g. june 2006).

More infos:
gnash bug:
http://savannah.gnu.org/bugs/?func=detailitem&item_id=16465
lists thread:
http://lists.gnu.org/archive/html/gnash/2006-07/msg00013.html
Comment 2 Andrew Williams 2006-07-17 09:28:24 UTC
Good. Nevertheless, a gentoo bug reported the same identical crash occurring
with another openGL application as well as gnash. I can't remember which one it
was now (cube something, maybe cube3d?) and the bug report has been removed, but
that does suggest it was triggering a more fundamental X server issue.
Comment 3 Andrew Williams 2006-08-01 22:14:46 UTC
I've been having the same crash with a couple of other GL programs. In
particular, the openGL version of jjffe (disassembled and tweaked version of
Frontier First Encounters - http://jaj22.org.uk/jjffe/) seems particularly adept
at tossing me out of X. Here's the error message, same as before:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x71) [0x480221]
1: /lib/libc.so.6 [0x2b07c950b600]
2:
/usr/lib64/xorg/modules/extensions/libGLcore.so(_mesa_update_draw_buffer_bounds+0)
[0x2b07dbd40cb0]

Fatal server error:
Caught signal 11.  Server aborting

I haven't been able to test this on my 32-bit machine, but if it's anything like
the gnash crash it's a genuine bug and not platform-specific.
Comment 4 Andrew Williams 2006-08-01 22:18:38 UTC
I should add, with both the gnash and jjffe crashes, the X server abort was
caused by CLOSING the application. In the case of gnash it was by pressing
'home' or going to another web page and in jjffe it was simply by exiting the
application. Both appeared to run without too many problems.
Comment 5 Michel Dänzer 2006-08-03 01:56:59 UTC
Can you try a newer Mesa CVS snapshot? Some issues like this have been fixed.
Comment 6 Andrew Williams 2006-08-03 06:14:48 UTC
Tried a cvs snapshot from today (3rd August) and get an identical server abort.
Every time without fail. Same error message.
Comment 7 Michel Dänzer 2006-08-03 07:12:14 UTC
I assume you rebuilt the X server against the new Mesa snapshot as well?
Comment 8 Andrew Williams 2006-08-03 07:43:33 UTC
I hadn't, but I have now with the same results.
Comment 9 Timo Jyrinki 2007-02-22 14:28:17 UTC
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status.

Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.


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.