358507 - Crash while displaying flash contents, i.e. from video.google.com

Status: RESOLVED DUPLICATE of bug 304370

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Description

[Vitaly Bordug]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.8.1) Gecko/20061010 Firefox/2.0

Flash player plugin cause the whole application crash, both with old 7.x and new 9.x beta plugins from Adobe. The same does not happen with 1.5.7 coming with FC5

Reproducible: Always

Steps to Reproduce:
1.load http://video.google.com
2. click on any movie thumbnail


Actual Results:  
Browser crash, no talkback window appears.

Expected Results:  
well, just movie display

I beleive that has a dup somewhere, but I failed to find. Most of bugfix requests are concerning win version...

TIA!

Comment 1

[Adam Guthrie]

If you launch Firefox from the command line, what do you see printed out when you crash?

Comment 2

[Vitaly Bordug]

The output and an attempt to backtrace below. No symbols in most of stuff, including FF and adobe .so stuff apparently.

[New Thread 61004688 (LWP 9831)]
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 117 error_code 8 request_code 146 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209043264 (LWP 9811)]
0x00411300 in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x00411300 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x06b569f8 in NP_Shutdown () from /root/.mozilla/plugins/libflashplayer.so
#2  0x06b9a362 in NP_Shutdown () from /root/.mozilla/plugins/libflashplayer.so
#3  0x06a64e3d in NP_Shutdown () from /root/.mozilla/plugins/libflashplayer.so
#4  0x069d8568 in ?? () from /root/.mozilla/plugins/libflashplayer.so
#5  0x069d0130 in ?? () from /root/.mozilla/plugins/libflashplayer.so
#6  0x06fd5780 in ?? () from /root/.mozilla/plugins/libflashplayer.so
#7  0x06fd51e0 in ?? () from /root/.mozilla/plugins/libflashplayer.so
#8  0xbfcabec4 in ?? ()
#9  0x06f30c9a in ?? () from /root/.mozilla/plugins/libflashplayer.so
#10 0x06f30c84 in NP_Shutdown () from /root/.mozilla/plugins/libflashplayer.so
Previous frame inner to this frame (corrupt stack?)
(gdb) 

Comment 3

[Vitaly Bordug]

To be clear: The upper comment was from sudo session, to exclude issues related to odd perms somewhere, and to get clear FF-2 + shockwave plugin instance. The same happens from the user perspective.

Comment 4

[timeless]

you'll need to build firefox with --enable-debug or --enable-debugger-info-modules and install a version of the flash player with symbols in order to get a useful stack trace.

Comment 5

[Adam Guthrie]

I'm pretty sure that this is a dupe of bug 304370, but just to be sure can you attach your xorg.conf (in /etc/X11/)?

Comment 6

[Vitaly Bordug]

Attachment: configuration when crash went away

Attaching just in case

Comment 7

[Vitaly Bordug]

Definitely, with 24bps the issue disappeared. OTOH, I have no composite extension, and 1.5.7 feels just fine with the same plugin/xorg.conf/etc. 

So although it might be something else, now it is working for me :)

*** This bug has been marked as a duplicate of 304370 ***

Comment 8

[BMO Automation]

Version and milestone values are being reset to defaults as part of product refactoring.