197937 - crash if JavaApplet keeps calling JavaScript functions for a while

Status: RESOLVED FIXED

(Core Graveyard :: Java: OJI, defect)

Description

[Larry Gao]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4a) Gecko/20030316
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4a) Gecko/20030316

Browser crashes if JavaApplet keeps calling JavaScript function by an interval.
I have a weblication where the JavaApplet needs to call JavaScript continually
by an interval. The mozilla browser for Solaris definitely will crash after a
while (sometimes in 1 minute, sometimes in 10  minutes). I have downloaded
Mozilla Release 1.0, 1.1b, 1.3.1b, 1.02, and the nightly build on 03/16. I
tested them on Solaris 8 and Solaris 9 with JavaPlugin 1.4.0_01. The problem
occured on all versions.
I also tested it on Mozilla for Windows 2000, it worked fine. So it seemed that
the problem only exists on the mozilla for Solaris.

To reproduce the problem, I wrote a simple example: An JavaApplet keeps calling
a javascript function, the javascript function does nothing but displayes a
message to indicate it is called by JavaApplet.
With this example, the mozilla has two responses:
1. crashes in 1 minute without any error message.
2. crashes in 10 minutes with the following error message:
/*
**************** SERVER ERROR **************
write_fully: Did not write everything pipe=10 4 -1
**************** ************ **************

**************** SERVER ERROR **************
write_fully: Did not write everything pipe=10 154 -1
**************** ************ **************
*/

In two cases, there is no core file dumped.


Reproducible: Sometimes

Steps to Reproduce:
1.Extract the attachment, put them in a web server.
2.If you have open the mozilla browser, close it.
3.Startup the mozilla browser.
4.Visit the TLiveConnect.html in the attachment.
5.Wait for 2 seconds, you will see there are messages shown in the textarea.
After you see the message, open the java console.
6.Wait for 1 minute. If the browser crashes, the problem is re-produced. If not,
go ahead to step 7.
7. Wait for 10 minutes. If the browser crashes, there will be also an error
message shown in the console where the mozilla was started. (See "details"
section for the error message).
8. If the browser is still working, that's fine. I seldom met this case. If it
is this case, clear the cache, shutdown the browser. Then repeat step 3.

Comment 1

[Larry Gao]

Attachment: Package to reproduce the problem

Comment 2

[Joshua Xia]

can't reproduce by using jre1.4.2-beta, reproduce on jre1.4.1_01, checking!

Comment 3

[Larry Gao]

Would you provide the URL to download jre 1.4.2-beta, I can not find it on
java.sun.com.

Thanks

Comment 4

[Joshua Xia]

Sorry! jre 1.4.2-beta can't be downloaded from external.

I will check if or not we can fix this bug on Mozilla side even though use jre1.4.1

Comment 5

[Larry Gao]

Attachment: Simplified version

This is the simplified sample to demonstrate the problem.
Both Java file and HTML file are simplified.

Now, the testing result is:
the browser runs for several minutes, then crashes with the error message:

INTERNAL ERROR on Browser End: Pipe closed during read? State may be corrupt
System error?:: Error 0

Comment 6

[Joshua Xia]

This bug has been fixed on JPI/JRE1.4.2-beta.
JPI exit JVM when it found write/read pipe error.

It seems that there is no way fix on mozilla side.

Comment 7

[Larry Gao]

Joshua Xia,

Do you notice that this problem only occurs on Solaris. It is working fine on
Windows 9X/2000.

So the JREs for Windows before 1.4.2-beta are different from the JREs for Solaris?

Comment 8

[Joshua Xia]

This part code (js/liveconnect) that on mozilla side is cross-platform, but Sun
's JPI implement on UNIX is different on Windows.

Comment 9

[Joshua Xia]

->fixed in JRE1.4.2 beta

Comment 10

[dsirnapalli]

-- Reporter, can you verify the test case using latest JRE(1.4.2_Beta). I donot
have access to SUNOS right now. Thanks.