Closed Bug 106169 Opened 23 years ago Closed 23 years ago

Crashes as soon as the page starts to load, causing the browser session to stop responding.

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tomr, Assigned: serhunt)

References

()

Details

(Keywords: crash)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012
BuildID:    2001101201

As you surf to a page with EITHER a java plugin or a flash plugin the web page
only gets partially (or not all at all) displayed and then the browser window
stops responding which cause all other open mozilla sessions to stop responding
as well.

Reproducible: Always
Steps to Reproduce:
1.Surf to a page with a java or flash plugin
2.wait for it to stop responding.
3.kill mozilla taking all other open browser sessions with you.

Actual Results:  The browser session crashed and stopped responding on trying to
load the plugin. It becomes very annoying because you can unintentionally surf
to a page that contains either of these plugins and lose research you were doing
in other mozilla windows.

Expected Results:  That the plugin would load fne, as it does in netscape. Or
the plugin should not load but mozilla should remain stable.

I am running:
CPU: p4 1.6ghz
RAM:256 meg
OS: Linux redhat 7.1
Reporter: Please try a talkback-enabled build:
http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu-sea.tar.gz

Then, if you get a crash, please post the Talkback ID here.

In addition, there is a known compatibility problem between mozilla, the Sun JRE
1.3.0 plugin and the 2.4 kernel with RH 7.1. For details, see:
http://bugzilla.mozilla.org/show_bug.cgi?id=84093 

Workaround: Upgrade your Java plugin to at least JRE 1.3.1 or set this
enviornment variable before starting mozilla: LD_ASSUME_KERNEL=2.2.5

-> critical
Severity: blocker → critical
Keywords: crash
wfm, linux 2001111408 ---> WORKSFORME

Reporter, reopen the bug if the problem still occurs on milestone 0.9.6.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.