Closed Bug 219351 Opened 22 years ago Closed 20 years ago

Loading Problem combined with JavaScript (not exactly describeable)

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: traumwandler, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.4) Gecko/20030624 We actually have the State in a bigger project (can't publize the source) that, if we restart our Server, the first two or three times we try to view the Project with Mozilla, it completely crashes(if it loaded one time, it works again, until the next restart of the server). I got an JavaScript Errormessage, that doesn't tell me a lot(to search the error-source): "Uncaught Exception: Permission denied to get Property UnnamedClass.filename." (this is short before the browser crashes) Sorry i havn't got more information now. Reproducible: Sometimes Steps to Reproduce:
Unfortunately, the information provided is totally inadequate to actually do anything about this bug. Could you provide a talkback incident ID? Or a stack trace? Also, does the page in question use a Java applet? If so, does taking that out fix the crash? Since we can't get access to the source, the only way we can do anything to fix this bug is if you give us all the information you can...
Hmm, there is no Java Applet and i guess it isn't a good idea to view more than 2000 lines JavaScript Code to rebuild. Talkback ID: lets see, i sent you one Talkback but i didn't noticed the ID ... hmm actually the test database is down too, so i can't rebuilt it *damnit* ... Stack trace isn't available too. The Errormessage i wrote was to from an Screenshot i made after the application crashed. ... I try to rebuild it an look inside the details for Talkback ID & Stacktrace (hope i'll find it there) [I'm now 2 days not reachable]
> but i didn't noticed the ID Run the talkback.exe program in the "components" directory of your Mozilla installation. This will list all the talkback incidents you have submitted and their IDs.
*hah* (me == stupid idiot :)) Talkback ID : TB23634864Q
David, could you get the stack? Sorry to bother you, but I'm not sure who still has access to talkback...
Incident ID: Incident ID 23634864 Stack Signature js_MarkGCThing b25fe158 Email Address traumwandler@traumwandler.com Product ID Gecko1.4 Build ID 2003062408 Trigger Time 2003-09-16 02:29:27 Platform Win32 Operating System Windows NT 5.1 build 2600 Module js3250.dll URL visited local (not available from the net) User Comments It seems that the browser loads itself to death. There occured an JavaScript Errormessage: "uncaught exception: Permission denied to get property UnnamedClass.filename" Trigger Reason Access violation Source File Name d:/builds/seamonkey/mozilla/js/src/jsgc.c Trigger Line No. 863 Stack Trace js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] JS_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsapi.c, line 1649] MarkScopeJSObjects [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 654] XPC_WN_Shared_Proto_Mark [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 1384] js_Mark [d:/builds/seamonkey/mozilla/js/src/jsobj.c, line 3605] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] JS_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsapi.c, line 1649] XPCWrappedNativeProto::MarkBeforeJSFinalize [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcprivate.h, line 1622] xpc_MarkForValidWrapper [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 685] XPC_WN_Shared_Mark [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 702] js_Mark [d:/builds/seamonkey/mozilla/js/src/jsobj.c, line 3605] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] JS_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsapi.c, line 1649] MarkScopeJSObjects [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 654] XPC_WN_Shared_Proto_Mark [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 1384] js_Mark [d:/builds/seamonkey/mozilla/js/src/jsobj.c, line 3605] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] JS_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsapi.c, line 1649] XPCWrappedNativeProto::MarkBeforeJSFinalize [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcprivate.h, line 1622] xpc_MarkForValidWrapper [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 685] XPC_WN_Shared_Mark [d:/builds/seamonkey/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 702] js_Mark [d:/builds/seamonkey/mozilla/js/src/jsobj.c, line 3605] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] js_MarkGCThing [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 863] gc_root_marker [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 971] JS_DHashTableEnumerate [d:/builds/seamonkey/mozilla/js/src/jsdhash.c, line 594] js_GC [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 1181] js_ForceGC [d:/builds/seamonkey/mozilla/js/src/jsgc.c, line 995] JS_GC [d:/builds/seamonkey/mozilla/js/src/jsapi.c, line 1662] nsJSContext::Notify [d:/builds/seamonkey/mozilla/dom/src/base/nsJSEnvironment.cpp, line 1671] nsTimerManager::FireNextIdleTimer [d:/builds/seamonkey/mozilla/xpcom/threads/nsTimerImpl.cpp, line 616] nsAppShellService::Run [d:/builds/seamonkey/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 479] main1 [d:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1284] nsAppShellService::Run [d:/builds/seamonkey/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 479] main1 [d:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1284] main [d:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1650] WinMain [d:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1672] WinMainCRTStartup() kernel32.dll + 0x214c7 (0x77e614c7)
x86 Registers: EAX: 00000000 EBX: 01e6b640 ECX: 00000000 EDX: 07fff300 ESI: 07ffe1f8 EDI: 0756023c ESP: 0012fff8 EBP: 00000000 EIP: 00000000 cf pf af zf sf of IF df nt RF vm IOPL: 0 CS: 001b DS: 0023 SS: 0023 ES: 0023 FS: 0038 GS: 0000
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.