Closed Bug 156440 Opened 23 years ago Closed 23 years ago

crash on page loading if javascript enabled

Categories

(Core Graveyard :: Plug-ins, defect)

PowerPC
Mac System 9.x
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 115917

People

(Reporter: bugzilla04.for.tormod, Assigned: rubydoo123)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.1a+) Gecko/20020708 BuildID: 20020708 Mozilla crashes when I go to http://geoscope.ipgp.jussieu.fr/~gaboret/ and javascript is enabled. If I disable javascript it is ok. Reproducible: Always Steps to Reproduce: 1. (Make sure Javascript is enabled for browser) 2. Go to the URL. Actual Results: Mozilla crashes immediately. Talkback ID TB8135017Q. Also Mozilla 1.1a crashes, talkback TB8133909Q.
Both stacks are the same: MRJPlugin + 0x12248 (0x3d2c34f8) MRJPlugin + 0x16d88 (0x3d2c8038) MRJPlugin + 0x1295c (0x3d2c3c0c) MRJPlugin + 0x141d8 (0x3d2c5488) ProxyJNIEnv::FindClass() [ProxyJNI.cpp, line 284] init_netscape_java_classes() [jsj.c, line 349] jsj_ConnectToJavaVM() [jsj.c, line 500] JSJ_AttachCurrentThreadToJava() [jsj.c, line 703] map_js_context_to_jsj_thread_impl() [lcglue.cpp, line 209] jsj_EnterJava() [jsj_utils.c, line 458] JavaPackage_resolve() [jsj_JavaPackage.c, line 167] js_LookupProperty() [jsobj.c, line 2293] js_GetProperty() [jsobj.c, line 2454] js_Interpret() [jsinterp.c, line 2574] js_Execute() [jsinterp.c, line 968] JS_EvaluateUCScriptForPrincipals() [jsapi.c, line 3379] nsJSContext::EvaluateString() [nsJSEnvironment.cpp, line 695] This is a crash in the Java plugin; not the JS engine.
Assignee: rogerl → beppe
Component: JavaScript Engine → Plug-ins
QA Contact: pschwartau → shrir
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is a dupe of 115917. Good to have a testcase. *** This bug has been marked as a duplicate of 115917 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Keywords: crash
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.