Closed
Bug 8382
Opened 25 years ago
Closed 25 years ago
Freeze with unconfigured proxy
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: girard, Assigned: warrensomebody)
Details
Hi,
Gecko 6 freeze trying to connect to cvs-mirror.mozilla.org...
I think this bug is relied to my network proxy. Usually I must configure the
network proxy parameter, but I don't known how to do that with Gecko 6.
Of course Gecko should not freeze if someone doesn't configure his proxy.
I include the console output of apprunner:
D:\gecko\bin>apprunner
width was not set
height was not set
The Messenger component is available. Initializing...
Messenger has been bootstrapped!
The Message Compose component is available. Initializing...
Composer has been bootstrapped!
Reading file...
Reading file...Done
Reading file...
Reading file...Done
Reading file...
Reading file...Done
Reading file...
Reading file...Done
Doing Startup...
Creating browser app core
BrowserAppCore has been created.
Setting content window
Reading file...
Reading file...Done
Init!
Reading file...
Reading file...Done
adding "http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey/flash.rdf" to
the tree
Connect: Contacting host: cvs-mirror.mozilla.org...
Hoping to test Gecko quickly,
Thanks
Yvan
girard@cn.ca
Assignee: don → warren
Component: Apprunner → Networking Library
Summary: Gecko freeze → Freeze with unconfigured proxy
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 1•25 years ago
|
||
This bug is fixed with M7 builds, which should be out shortly. You are correct,
you shouldn't hang.
For information on setting your proxy, please see bug 8559 for the current state
of proxy prefs, by the way. They were working, but are basically broken now,
though you can get it to work (read bug). For now, you need to manually enter
the prefs into your prefs50.js file by grabbing them from your 4.x prefs.js
file.
Comment 2•25 years ago
|
||
Verified with 6/21 M7 builds. Pulled network cable out, and browser still came
up.
Changing all Networking Library/Browser bugs to Networking-Core component for
Browser.
Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do
this in a bulk change. If this happens, I will fix. ;-)
Bulk move of all Networking-Core (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
•