Closed Bug 198920 Opened 21 years ago Closed 21 years ago

Browser locks up right after the flash intro

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: gabor.k.horvath, Assigned: peterlubczynski-bugs)

References

()

Details

(Keywords: hang)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

The browser locks up if I click "skip intro" or I wait for it to finish.
The second is not so sure.

flash player: Shockwave Flash 6.0 r79
Java: Blackdown Java-Linux Java(TM) Plug-in1.4.1
Mozilla was hand installed from the ...sea.tar.gz package.

I am running Debian SID. Using a corporate proxy. I don't even know its name...


Reproducible: Always

Steps to Reproduce:
1.load http://www.eurofighter.com
2.click skip intro
3.Mozilla hangs

Actual Results:  
mozilla stopped responding

Expected Results:  
loading some page about a jetfighter...
Oh my...
I forgot, I am using ALSA, and ESD. Started mozilla with 
"esddsp /opt/mozilla/mozilla"
These used to have some effect on mozilla's behaviour.
does it work when you don't start Mozilla with esddsp ?
Assignee: asa → peterlubczynski
Component: Browser-General → Plug-ins
Keywords: hang
QA Contact: asa → bmartin
Yes it does.

It works for me if I leave out esd.

Funny thing that I had to start using esd and its wrappers exactly because flash
plugin locked when it could not open /dev/dsp. Now it locked because I used ESD...
Sometimes I wish I used windows...

Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
reopening to resolve as WFM as no specific patch fixed this bug.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Marking WFM as per reporter comments.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
Marking Verified WFM
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.