189761 - [gtk2] mozilla crashes while viewing *.swf with flash5 plugin

Status: RESOLVED DUPLICATE of bug 304370

(Core :: XUL, defect)

Description

[Robin Lu]

Use moz+gtk2.2 on Solaris to view the URL
http://www.blam.com/Bump_Intro/bump%20intro%20with%20sound.swf
result: mozilla crashes

It is ok for moz+gtk2.0 on linux and moz+gtk1.2 on both of linux and solaris.

The crashes happens when gtk2xtbin dispatches a timer event to flash plugin.
While handling the timer event, libflashplayer.so first changes the size of the
plugin window to a invalid size. Sometimes, an x error could be generated here.
If the size is not invalid enough to generate an x error, mozilla crashes when
libflashplayer.so tries to PutImage and malloc, I guess, according to the size.
Anyway, the root cause is the invalid size.

Comment 1

[Robin Lu]

It seems like moz+gtk2 triggers some bug of flash5 plugin. My moz+gtk2 at linux
was OK because I was using flash6beta. When I changed back to flash5 plugin, the
above URL doesn't work either. Wish I could have a look at flash plugin code.

Comment 2

[Ari Pollak]

Is this really a bug if the Moz Release Notes say that Flash5 should not be
used, but rather Flash 6?

Comment 3

[Robin Lu]

not really.
Because moz+gtk2 crashes more easily than moz+gtk1.2 in this situation while the
release note if for moz+gtk1.2. There might be something not quite right for
moz+gtk2, so we have to keep a notice here. I suspect it is due to size
allocation of gtksocket.

Comment 4

[John M]

This should be closed. Flash7 is out.

Comment 5

[uamjet602]

I still have this problem with flash 7:

Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10

File name: libflashplayer.so
Shockwave Flash 7.0 r25

It crashes with:

The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 117 error_code 8 request_code 146 minor_code 3)

every time I open a flash, for example the url in this bug. I tried running with
--sync but it made no difference.

Comment 6

[timeless]

[e-mail], --sync isn't supposed to prevent you from
crashing (or exiting), i think
http://www.unixos2.org/sw/pub/docs/porting/debugging.html#xerrors should be
helpful for getting a stack trace to the bad match.

Comment 7

[timeless]

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