Crash due to Java (INTERNAL ERROR on Browser End: Pipe closed during read?...)



15 years ago
8 years ago


(Reporter: vincent-moz, Assigned: joshua.xia)




Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.5a) Gecko/20030708
Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.5a) Gecko/20030708

I went to the above page. I could see that the Java plugin couldn't be started
(see below). I closed the tab and Mozilla crashed. Here's what was written in
the console:

java_vm: relocation error:
/usr/local/j2re1.3.1/lib/ppc/native_threads/ symbol __divdi3, version
GLIBC_2.0 not defined in file with link time reference
Finished ReadPrefs OK
Document loaded successfully
java_vm: relocation error:
/usr/local/j2re1.3.1/lib/ppc/native_threads/ symbol __divdi3, version
GLIBC_2.0 not defined in file with link time reference
INTERNAL ERROR on Browser End: Pipe closed during read? State may be corrupt
System error?:: Resource temporarily unavailable

Reproducible: Didn't try

Steps to Reproduce:

I haven't tried to reproduce this crash, but a similar crash occurred on another
Java page.

Comment 1

15 years ago
that's a JVM issue (I guess you're using blackdown), perhaps file a bug report
to this group or wait for 1.4.1 ppc ?
wfm using build 2003072105 on Linux x86 + Sun's JRE 1.4.2.
Keywords: crash

Comment 2

15 years ago
Note that the bug is not the fact that the JVM can't be started (there are
problably libraries compiled with a different compiler or something like that,
I'll have to see if I can solve this problem), but the fact that Mozilla
crashes. If there is a problem with the JVM, Mozilla shouldn't crash.

(And FYI, it seems that there is no plan for 1.4.x for PPC.)

Comment 3

15 years ago
then it's dupe of bug 180946 or bug 156493.

Comment 4

15 years ago
Not bug 180946, since Mozilla didn't exit immediately. Well, in fact, I could
see a java_vm process; so, it started, but not completely.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED


8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.