Closed
Bug 112969
Opened 23 years ago
Closed 23 years ago
PAC: PAC hangs/crashes on startup.
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: benc, Assigned: selmer)
Details
(Keywords: crash)
Netscape 6.2.1 FC
Probably because it tries to load the home page, the SOCKS directive that goes
nowhere during normal usage also hangs (and occassionally crashes) Netscape and
Mozilla on startup:
STEPS:
Set a PAC file that always results in "SOCKS" directive. Then quit and restart
(try: http://www.packetgram.com/pktg/proxy/pac/pacfiles/socks.pac)
When you restart, select the same profile you used before, and then observe that
it hangs.
[root@h-10-169-111-76 netscapeDailyTrunk]# ./netscape &
[1] 1228
[root@h-10-169-111-76 netscapeDailyTrunk]# ./run-mozilla.sh ./mozilla-bin
MOZILLA_FIVE_HOME=/usr/local/netscapeDailyTrunk
LD_LIBRARY_PATH=/usr/local/netscapeDailyTrunk:/usr/local/netscapeDailyTrunk/Cool
LIBPATH=/usr/local/netscapeDailyTrunk:/usr/local/netscapeDailyTrunk/Cool
SHLIB_PATH=/usr/local/netscapeDailyTrunk:/usr/local/netscapeDailyTrunk/Cool
XPCS_HOME=/usr/local/netscapeDailyTrunk/Cool
MOZ_PROGRAM=./mozilla-bin
MOZ_TOOLKIT=
moz_debug=0
moz_debugger=
ProfileManager : StartApprunner
profileName passed in: Default User
I am inside the initialize
Hey : You are in QFA Startup
(QFA)Talkback loaded Ok.
Sometimes it returned a 127 error after about 30 minutes.
I haven't had time to look at other platforms.
Ben, do you have a stack handy?
stephend: Nope. But the offending system is down the hall from you.
How do I get the info you need?
*** This bug has been marked as a duplicate of 99026 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Summary: PAC: SOCKS directive PAC hangs/crashes on startup. → PAC: PAC hangs/crashes on startup.
If you can still get it to crash on a nightly build, Talkback should come up,
simply report the Incident ID and we can pull a stacktrace from that.
That never happened w/ this bug, even though talkback worked for other bugs.
Oh well, Darin thinks this is fixed anyhow.
You need to log in
before you can comment on or make changes to this bug.
Description
•