Closed
Bug 9020
Opened 26 years ago
Closed 25 years ago
Error Loading URL when choosing the different search engine site
Categories
(Core :: Networking, defect, P2)
Tracking
()
M10
People
(Reporter: teruko, Assigned: brendan)
References
()
Details
Tested 6-28-08 Win32 build under Win95J and Winnt 4.0J.
Step of reproduce
1. Launch Apprunner
2. Go to the above URL
3. Click on the different search engine site. For example, "Netscape"or "goo"
Notice that Apprunner does not go to the selected site.
"Error Loading URL http:// " is shown.
Reporter | ||
Updated•26 years ago
|
Priority: P3 → P2
Target Milestone: M9
Updated•26 years ago
|
Assignee: ftang → don
Assignee: don → warren
Component: Internationalization → Necko
Target Milestone: M9
Updated•26 years ago
|
Assignee: warren → gagan
Target Milestone: M9
Comment 1•26 years ago
|
||
Gagan, can you look at this one?
Assignee | ||
Updated•25 years ago
|
Assignee: brendan → gagan
Comment 3•25 years ago
|
||
Is this about javascript: not working? If so, it's a DUP of 1646 or the new
since M9 14049. If you really ran into 14049, you'd assertbotch a debug build.
If you didn't, but were running debug, then this is not a javascript: bug.
Could you reassign or mark DUP based on the facts above? Thanks,
/be
Reporter | ||
Comment 4•25 years ago
|
||
Talkback Incident 13736463
Trigger Type: Program Crash
Trigger Reason: Access violation
Call Stack: (Signature = js_LockScope1 6a02672b)
js_LockScope1
[d:\builds\seamonkey\mozilla\js\src\jslock.c, line 631]
js_LockObj
[d:\builds\seamonkey\mozilla\js\src\jslock.c, line 705]
js_SetProperty
[d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 1905]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2208]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 675]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2229]
js_Execute
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 829]
JS_EvaluateUCScriptForPrincipals
[d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 2617]
nsJSContext::EvaluateString
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 188]
nsJSInputStream::Eval
[d:\builds\seamonkey\mozilla\dom\src\jsurl\nsJSProtocolHandler.cpp, line 166]
nsJSInputStream::Available
[d:\builds\seamonkey\mozilla\dom\src\jsurl\nsJSProtocolHandler.cpp, line 106]
nsFileTransport::Process
[D:\builds\seamonkey\mozilla\netwerk\base\src\nsFileTransport.cpp, line 504]
Brendan: I couldn't make out much from this stack trace except that its js
related. You'd have to look into this. Thx.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 6•25 years ago
|
||
Pretty clearly a dup of 14049, on warren's list (I'm fixing). Thanks for the
stack, teruko.
/be
*** This bug has been marked as a duplicate of 14049 ***
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 7•25 years ago
|
||
Verified as dup.
Bulk move of all Necko (to be deleted component) bugs to new Networking
component.
You need to log in
before you can comment on or make changes to this bug.
Description
•