Mark Reporter
	Description • 23 years ago

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20010913
BuildID:    2001091303

After installing Mozilla, I noticed that Java was not installed.  I followed the
link to the Netscape web page and proceeded to download the JRE XPI.  On
completion of the download, the browser crashed and the feedback agent started.
 The JRE installer continued.  Upon restart of the computer I went to the Java
homepage and still saw the Java plugin did not load.  Using "About Plugins", I
noticed that the plugin did exist.

Reproducible: Always
Steps to Reproduce:
1.  Went to Sun's Java home page
2.  Followed the Netscape link to download the Java Plugin
3.  During the XPI install, the browser crashed but install continues
4.  Restart computer
5.  Return to Sun's Java home page (applet still not loaded)

Actual Results:  When the Java home page opens, the place where the applets
should exist has a small icon which says to click on it to download the
appropriate plugin.  Permission is requested to install and after the download,
browser crashes.  Install of the JRE continues.

Expected Results:  The Applet should load from the Sun web page (a scrolling
news ticker.)  Installing the XPI should work correctly by installing the Java
Runtime Environment.  (Browser should not crash during install.)

The Talkback Crash ID was TD35478506Q.
Seems similar to #96867

	K'Trina Medina
	Comment 1 • 23 years ago

Marking this as a duplicate of bug 96867. 



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

	K'Trina Medina
	Comment 2 • 23 years ago

Reopening bug. ccing rudman and endico.

Per Mark (mb_add@yahoo.ca): 
When looking at this, it did not state anywhere that the browser crashed (which 
happened when I went through the install.)  As I read #96867, it just looked 
like the plugin was not installed in the correct location.  For my situation, 
the browser downloaded the XPI for the JRE and it looked like an installer 
started in the background which caused the browser to crash (which is why I 
included the Talkback ID.)

	Daniel Veditz [:dveditz]
	Comment 3 • 23 years ago

Here's the stack:
js_AllocRawStack [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 342]
js_AllocStack [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 374]
JS_PushArgumentsVA [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 293]
JS_PushArguments [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 267]
handleTriggerEvent
[d:\builds\seamonkey\mozilla\xpinstall\src\nsXPITriggerInfo.cpp, line 148]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 524]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1072]
KERNEL32.DLL + 0x24407 (0xbff94407)
0x00688b62 

Looks like it's crashing when there's a trigger callback on the website, but not
all the time or we'd get a lot more of these. Bug 96867 has nothing to do with
this one.

	Daniel Veditz [:dveditz]
	Comment 4 • 23 years ago

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

	Daniel Veditz [:dveditz]
	Comment 5 • 23 years ago

sorry for spam, finger slipped on the number

	Daniel Veditz [:dveditz]
	Comment 6 • 23 years ago

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

	Grace Bush
	Comment 7 • 23 years ago

verified