134282 - hang on loading flash plugin

Status: VERIFIED DUPLICATE of bug 58339

(Core Graveyard :: Plug-ins, defect)

Description

[Jonathan Ryshpan]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020310
BuildID:    2002031008

Pressing the "Home" tab at the upper left of this page causes Mozilla to lock
up.  A number of Mozilla processes are left running; but Mozilla won't respond
to any mouse or keyboard input.  It's possible to stop Mozilla by killing the
first three (in the ps list) of these processes.

Reproducible: Always
Steps to Reproduce:
1.Open URL http://www.alamedacountyfair.com/2001fair.html
2.Press the "Home" tab at the upper left of this page.


Actual Results:  Mozilla locks up.

Expected Results:  Displayed the URL.  (Don't know what's on it -- can't display
it.)

Why do you want us to get a Mozilla/Bugzilla ID?  This form is enough trouble
without!

Comment 1

[Vadim Berezniker]

I can't reproduce this in either mozilla 0.9.9 or trunk build #2002032800

Comment 2

[Andrew Schultz]

could you try a recent nightly build?

Comment 3

[Jonathan Ryshpan]

This appears to be related to some kind of networking problem.  I have just
upgraded my BIOS.

I will investigate further.  In the meantime, you can regard this bug as
unconfirmed.

Comment 4

[Jonathan Ryshpan]

Attachment: State of Mozilla at the time of lockup.

ps falwx | fgrep -i mozilla

Comment 5

[Jonathan Ryshpan]

I've dinked with the networking setup a good deal, including installing a new
brand of ethernet interface card (Netgear FA311 <natsemi driver> changed to
Kingston KNE111TX <tulip driver>).  The lockups seem to change in frequency; but
the given site *always* locks up Mozilla.  When Mozilla locks up, all 8 Mozilla
processes are sleeping on something: I've attached an extract of "ps falwx"
showing the Mozilla processes.

If anyone would like more info, please ask me for it.

Comment 6

[Andrew Schultz]

do you crash if you hold down the mouse button on "Home" and drag it off?  or
only if you single-click?

there are a couple other things you could try
1) try with Javascript disabled
2) try a nightly build.

Comment 7

[Jonathan Ryshpan]

The problem appears to be related to displaying Shockwave Flash data using the
Macromedia Flash Player 5 plugin.  Removing the files ShockwaveFlash.class and
libflashplayer.so from .../mozilla/plugins makes the crashes stop (and, of
course makes Shockwave Flash URLs undisplayable.  The problem seems to be
exactly as bug 126510.

The problem seems to be well known, since Matthew Cline (matt at
nightrealms.com) mentions it in a posting at:
  http://crossover.codeweavers.com/pipermail/support/2002-January/001090.html

Probably the description and status of this bug should be changed, but I'm
unwilling to do this, since I'm not familiar with the customs of this list/database.

Comment 8

[Andrew Schultz]

The URL does not have a Flash animation, but the URL you would go to does have a
flash animation.  Do you hang if you go straight to the link

http://www.alamedacountyfair.com/

Also bug 126510 is a "crash" (browser dies) rather than a "hang" (browser locks
up).  More likely a dupe of bug 58339.  Do you have audio playing from another
application (xmms)?  If so, this can cause the hang, so try stopping the audio
and see if you still hang.  If that fixes it, this is a dupe of bug 58339.

Comment 9

[shrirang khanzode]

wfm on 0327 trunk linux(redhat 7.1)

Comment 10

[Jonathan Ryshpan]

The lockup appears to be inside Flash.  I had a problem with my sound
configuration, which caused attempts to open /dev/dsp to fail with the error
code -EBUSY.  When I cured this problem, and /dev/dsp opened OK, the problem
went away -- ie. Mozilla no longer locks up.  It would be nice if there were
some kind of a timer that would raise an alarm when a plugin locks up; but maybe
this is too much to ask.

Probably the description and status of this bug should be changed, but I'm
unwilling to do this, since I'm not familiar with the customs of this list/database.

Comment 11

[Vadim Berezniker]

This is a dupe of bug 58339 then.
That bug has some workarounds if you're interested.

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

Comment 12

[shrirang khanzode]

v