Closed Bug 127845 Opened 23 years ago Closed 15 years ago

Proxy: Adsubtract + Windows XP crashes on reboot

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mozilla, Unassigned)

References

Details

(Keywords: crash)

Attachments

(1 file)

Image of proxy settings
52.20 KB, image/jpeg
Details 
At bootup, following a switch between users during the previous use of the
computer, I see two Adsubtract icons in the task bar, then it loads Mozilla
0.98+ (Netscape 6) browser and tells me that it can't find Adsubtract-local.
There are at least two dialog boxes telling me this. I close those dialog boxes
and am presented with the Adsubtract Fast-Switching notice (which is strange
because there is only one current user). I close that dialog box. I am not sure
if I close mozilla but the next thing I recall, the full circle (mozilla quality
assurance) program has started and reported the error back to netscape. I send
the error message via Full circle, and start mozilla. It starts just fine but on
closer inspection has deleted the proxy setting. I manually type Adsubtract and
port 4444 for the proxy and Mozilla now works fine through the Adsubtract proxy.

I am using the latest version of Adsubtract 2.45 and XP with all bug fixes. The
Incident ID for talkback is TB3380988E.

I have also filed a bug report with Adsubtract.
OS: Windows 2000 → Windows XP
-> networking for investigation/triage
Assignee: darin → new-network-bugs
Component: Networking: HTTP → Networking
QA Contact: tever → benc
Upon further analysis, I think this bug can be broken apart as follows:

* Adsubtract has a bug related to multiple users which arises in the form of a
dialog box and perhaps multiple instances of Adsubtract in the bootup following
a session where 2 users were logged on at the same time (switch users) in xp.

* I believe that during this time period (until you agree to the dialog box and
one instance of Adsubtract disappears) there is no network connectivity.

* Mozilla will bomb on startup if there is no network connectivity. Another way
to see this is on a laptop which is not connected to the Internet and which
requires a manual connection of PPPoE in XP to establish a connection to the
Internet (i.e. Verizon Avenue has some residential configurations that give you
a LAN connection but not an internet connection until you have authenticated).

* If Mozilla cannot connect to a proxy, it deletes the proxy listing from
preferences (It also has a nasty habit of doing this on upgrades too).
bug 137878 is about another installation oddness with the Addsubtract app.
As stated here, there seems to be an installation bug in the app.
Yes, Adsubtract has issues with Windows XP. But, from the perspective of the
browser, Adsubtract is nothing more than a proxy. Granted, the operating system
is connected to the internet independent of the proxy. But if Netscape is
configured to use the proxy, that point is irrelevant.

So, the proxy either talks to Netscape as it expects or it doesn't. Either way,
Netscape shouldn't bomb or change the proxy settings. A dialog box saying,
"Sorry, we couldn't connect because your proxy is tempermental..." would be far
more graceful.

See Talkback Incident TB5341814G.
Each problem should be filed as a separate bug.

Let's keep the crashing activity in this bug.

+crash, so eng will see it in their query that scans for crashes.
Keywords: crash
reporter: any update on how this is working?

Let me comment on a couple items you have raised:

mozilla crashing - I don't think this happens normally if there is no network
connection, instead you should get a "hostname not found" error b/c DNS lookups
would be the first to fail.

loosing proxy preferences - we've had occasional reports of that, but nothing we
could verify.
Blocks: 163294
No change. You can still get the latest version of Adsubtract to crash the
latest version of Mozilla, simply by installing Adsubtract and rebooting your
computer.

There was a crash that I reported using the automated crash reporting tool when
I uninstalled and reinstalled Adsubtract several weeks ago. I use Adsubtract Pro
(because I paid for it) but I am willing to bet that the free version of
Adsubtract will also result in a crash of Mozilla (and you could duplicate my
problem that way). 

If you leave the Netscape setting (under the browser tab) enabled, then Mozilla
crashes following every reboot. At bootup, the proxy attempts to reset the
selected browsers' proxy settings. For whatever reason, Adsubtract informs you
that it has issues with fast user switching--even though it is rebooting, not
switching between users--and even though you had only one user logged on in the
previous session.

If you disable the Netscape setting and manually assign the HTTP proxy in
Mozilla (127.0.0.1:4444), then no crashes result and only one Adsubtract icon
appears in the taskbar at bootup.

In summation, the problem continues and there is a work around. The problem is
due to the use of a specific Adsubtract setting but the issue should be
investigated further by Mozilla because the browser shouldn't crash when one
changes the proxy settings (so find out what the proxy is changing in order to
fix whatever is causing the crash). Also, refer to evangelism to get corrective
action by Adsubtract's developers.
reporter: can you still reproduce this bug with a recent build of mozilla (for
example, 1.2beta)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.
Yes it still occurs all the time, even in the latest builds of Mozilla and Phoenix.

I have even expressly noted such in recent Talkback reports, which are sent in
whenever I reboot my computer.

Beyond that, I am not sure how much more detailed I can be. Have you installed
Adsubtract on XP? And rebooted? And not experienced this issue?
->NEW.

If there was a crash, then we know this is real. I treat new and uncofirmed as
the same, but maybe someone isn't looking at crashers that aren't NEW...

reporter: please keep this open until it either goes away, or we figure out what
is going on. I do want to look at this, but unfortunately I have many other
things that need attention as well.
Status: UNCONFIRMED → NEW
Ever confirmed: true
reporter: I know you've posted a couple already, but may as well get a recent
one - can you crash it again with a recent mozilla build and post another
talkback ID so we can get the stack info in here? thanks
Keywords: stackwanted
Darin, do you have a meta bug for "spam blocking" incompatiblites?  
so, we are talking only about some version of netscape 6 here?  and does the
proxy require authentication (username and password)?  if so, then i may know
the cause of the crash.

does the problem occur with the latest mozilla nightly build?  or how about with
mozilla 1.2 beta?
nevermind my last comment... i overlooked comment #9.
Microsoft Error Report:

Error Signature:
AppName: mozilla.exe	 AppVer: 1.2.0.0	 ModName: js3250.dll
ModVer: 4.0.0.0	 Offset: 00002a28

===================================================================

Netscape Quality Feedback:

Incident ID: TB14189289H
Captured: 11/20/2002 5:09PM
Type: Program Crash
Comments: See Bugzilla Bug 127845
js3250.dll + 0x2a28 (0x61052a28)
jsj3250.dll + 0x48d0 (0x61e248d0)
js3250.dll + 0x27547 (0x61077547)
js3250.dll + 0x26990 (0x61076990)
js3250.dll + 0x29123 (0x61079123)
js3250.dll + 0x26623 (0x61076623)
js3250.dll + 0x18ca1 (0x61068ca1)
js3250.dll + 0x3c53 (0x61053c53)
xpc3250.dll + 0x12a27 (0x610c2a27)
xpc3250.dll + 0x14188 (0x610c4188)
xpc3250.dll + 0x14f3c (0x610c4f3c)
js3250.dll + 0x27402 (0x61077402)
js3250.dll + 0x27a2e (0x61077a2e)
js3250.dll + 0x1ef16 (0x6106ef16)
js3250.dll + 0x1aed9 (0x6106aed9)
js3250.dll + 0x454d (0x6105454d)
jsdom.dll + 0x3950 (0x61423950)
gkcontent.dll + 0x80e3c (0x61510e3c)
gkcontent.dll + 0x809cb (0x615109cb)
gkcontent.dll + 0x804e5 (0x615104e5)
gkcontent.dll + 0x82a4b (0x61512a4b)
urildr.dll + 0x14ea (0x612914ea)
chrome.dll + 0x1526 (0x612d1526)
xpcom.dll + 0x31067 (0x61dc1067)
xpcom.dll + 0x30fd3 (0x61dc0fd3)
xpcom.dll + 0x314c0 (0x61dc14c0)
USER32.dll + 0x3d91 (0x77d43d91)
USER32.dll + 0x438c (0x77d4438c)
appshell.dll + 0x7388 (0x61897388)
MOZILLA.EXE + 0x2057 (0x00402057)
MOZILLA.EXE + 0x1b40 (0x00401b40)
MOZILLA.EXE + 0x36c3 (0x004036c3)
MOZILLA.EXE + 0x77a8 (0x004077a8)
kernel32.dll + 0x214c7 (0x77e814c7)
Keywords: stackwanted
Product ID  Mozilla1.2
Build ID 2002111419
The problem sounds like it rooted in the combination of Mozilla & Adsubtract. So
if you configure mozilla to have no proxy setting, and reboot, does mozilla
still crash when it runs? This would isolate the problem to being either a "they
are both loaded crash" or a "they have a networking-level problem crash".
Summary: Adsubtract proxy, Mozilla, Windows XP, multiple users → Proxy: Adsubtract + Windows XP crashes on reboot
Attached image Image of proxy settings — 
Please see comment #7. I believe that the problem is rooted in Adsubtract's
default of rewriting Mozilla's proxy settings upon reboot.

Initially, I would suggest that the problem is rooted in the PAC (proxy
autoconfiguration) script processing. This would seem consistent with the
Program Crash Error Report referencing js3250.dll. However, Adsubtract appears
in the manual as contrasted with the automatic field (see attached image).
One other update:
Today's crash report was based on the latest version of Adsubtract, 2.54.
Okay. Re-writing of prefs is kind of unusual, and probably is done via prefs.js.

Can you look at your prefs.js and copy the values of "network.proxy.*" ? Maybe
there is a bad pref value that mozilla dislikes.

Here are the requested settings from prefs.js:

user_pref("network.proxy.http", "AdSubtract");
user_pref("network.proxy.http_port", 4444);
user_pref("network.proxy.type", 1);

There is no user.js.
per bug 181135: all bugs owned by previous default owner that were not futured
are being reassigned to default owner.
Assignee: new-network-bugs → dougt
over to darin for investigation.
Assignee: dougt → darin
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity.  Only changing open bugs to
minimize unnecessary spam.  Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.
Severity: normal → critical
-> default owner
Assignee: darin → nobody
QA Contact: benc → networking
Since Adsubtract doesn't seem to be available anymore can we mark this bug as CLOSED?
Well, this bug is not about Adsubtract, but the crash it caused. Given that there has been nothing new for over 6 years, I don't imagine there's anything useful that can be drawn from this report now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: