All Mozilla components lock up when loading the URL

VERIFIED DUPLICATE of bug 58339

Status

()

Core
Plug-ins
VERIFIED DUPLICATE of bug 58339
16 years ago
16 years ago

People

(Reporter: Duke, Assigned: rubydoo123)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020313
BuildID:    20020313

When attempting to load the provided URL, all components of Mozilla lock up. 
There is no response, not even to the "close" button on the title bar.  I have
to shutdown Mozilla using xkill, then reload it.  When shading and unshading or
minimizing and maximizing the windows, no graphics come up, just the
border/frame of the window.  Also, moving other windows over the Mozilla windows
leaves graphical "remnants" or trails.

Reproducible: Always
Steps to Reproduce:
1. Load the above URL, either by clicking on a link, or entering it in the URL bar
2. Mozilla locks up
3. Load xkill..

Actual Results:  After a black screen comes up, and the website title, "Document
Done" is displayed in the status bar.
Mozilla locks up, as described above.

Expected Results:  Load the web site, proceed to operate normally, respond to
commands and actions.

I have the following plugins installed:
Java(TM) Plug-in 1.3.1-b24
Shockwave Flash 5.0 r47

Using another browser, I found that the Flash 5 plugin is required.  I'm
guessing that's the source of the problem.

Comment 1

16 years ago
works nicely for me on 0408 trunk with flash 5.0r48

Comment 2

16 years ago
is /dev/dsp busy when this occures? (playing music, xmms or other)
Suspect dup of bug 58339
(Assignee)

Comment 3

16 years ago
works like a champ on win32, MacOSx and linux on today's builds. Can you get a 
more recent build and try this again?
(Reporter)

Comment 4

16 years ago
Yep, seems like it's a duplicate of bug 58339.
I had xmms playing some tunes while trying to load the page.  I closed xmms and
tried to load the page and it worked fine.
Thanks :)

*** This bug has been marked as a duplicate of 58339 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE

Comment 5

16 years ago
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.