Closed Bug 69944 Opened 25 years ago Closed 24 years ago

Conn: hang if Remote Access disconects

Categories

(Core :: Networking, defect)

PowerPC
Mac System 9.x
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: florian, Assigned: gordon)

References

Details

(Keywords: hang, regression, Whiteboard: [adt3 RTM])

If remote access disconects the connection the mozilla doesn't do anything and you can't switch between the applications. Very annoying. Mac OS 9.1
ouch
Assignee: asa → neeti
Component: Browser-General → Networking
Keywords: crash
QA Contact: doronr → tever
cc gordon. When you say 'remote access', do you mean PPP?
yes that's what i meant.
What kinds of things were you doing with mozilla before you were disconnected? Browsing any secure sites? IMAP? POP? FTP? This information may help us track down which areas of the code are not getting notified of the disconnection, or not responding to the notification properly.
I got this hang when I launched mail while remoteaccess was still making connection. Mozilla could not do anything even after connection was established. 2001022304 build.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This probably is not restricted to Remote access. I got a similar hang when I switched from Airport to Ethernet without switching TCP/IP and then started Mail/News.
i hang when i do that on my powerbook (see other bugs), but it resolves itself in 30 seconds or less. it never crashes.
I retract my previous comment. It really hangs in Remote Access, but not in Ethernet or AirPort.
Target Milestone: --- → mozilla0.9.1
I have experienced this problem too--Mozilla hangs if I disconnect Remote Access (PPP) via the Control Strip or the Remote Access control panel. I have to force quit Mozilla to regain control.
This might be related to bug 60204 and bug 69285 (hangs after waking from sleep after visiting a secure site or using the Password Manager). The symptoms are similar, and I just tried disconnecting Remote Access while I had Mozilla open but before I had visited a secure site or activated the Password Manager. The hang didn't happen.
Question for mozilla.org@pidgin.org: How long do you wait on Mozilla to un-freeze before you decide to force quit it? pinkerton notes seeing a 30 second hang and I believe some OT calls have a 2 minute timeout.
re: the question in the previous comment, I waited about 30 seconds to a minute and control didn't come back. I didn't try waiting around a lot longer than that.
In case of Get message in Mail(POP) while disconnected via Remote Access, the hang is complete. It is much longer than a few minutes before I have to force quit Mozilla.
Severity: normal → critical
*** Bug 73839 has been marked as a duplicate of this bug. ***
seems like this is mac specific. any one want to volunteer to track this down?
Keywords: crash → hang, helpwanted
Summary: Crash if remote access disconects → hang if remote access disconects
Target Milestone: mozilla0.9.1 → mozilla1.0
mass move, v2. qa to me.
QA Contact: tever → benc
My current problem is not that Mozilla "hangs" but rather that once my connection is reestablished, Mozilla must be quit and reopened to access anything online. All attempts to load web pages, newsgroups, etc. result in endless throbber action. Apparently I'm not alone in this -- this was one of Charles Moore's criticisms of 0.9 on http://www.applelinks.com/ a day or two ago. Is there a separate bug for this problem, or should this problem be considered part of this bug? Mac OS 9.1, Build 2001051811.
This should probably be gordon's bug, since it's likely an NSPR problem. Useful link: <http://developer.apple.com/technotes/tn/tn1145.html>
I think this is likely a dup of bug 69285, probably related to the pollable event implementation on the Mac.
this is a serious problem. assigning to gagan, this isn't neeti's issue.
Assignee: neeti → gagan
Keywords: nsbeta1, nsCatFood
Target Milestone: mozilla1.0 → ---
ok, silly me for not reading everything. let's give this to gordon.
Assignee: gagan → gordon
Setting target milestone to 0.9.1, because this is related (possibly a dup) of bug 69285, which is also slated for 0.9.1.
Target Milestone: --- → mozilla0.9.1
Since I'm going to be travelling for the next few days, and therefore using dialup connections, I'll apply the patch for 69285 and see what happens.
The patch for bug 69285 has just been checked in, and fixes this problem as well. Marking FIXED.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
WFM on Build 2001053005 on Mac OS 9.1 -- was able to browse several web sites, disconnect and reconnect via Remote Access, and then browse several other web sites. (Did not work on yesterday's build, so make sure you get today's.)
Summary: hang if remote access disconects → Conn: hang if Remote Access disconects
+verifyme reporter: tommybee99@yahoo.com says the fix works for him. Can I mark this as VERIFIED?
Keywords: helpwanted → verifyme
I had'n any ;-) problems with Mozilla since then. So it's probably solved.
florian: if you like, you can mark your own bugs "VERIFIED", and brag to your friends that you filed a bug and it was fixed :)
OK. Sorry. So then i have the great honor... ;-)
Status: RESOLVED → VERIFIED
You get the idea:) first people file bugs, then they close them... then they start learning to do builds, writing specs, running test cases... maybe eventually add a missing feature they want, like Digest Auth. Okay...bad example... :(
Keywords: verifyme
Reopenineg. I have experienced this hang in 20020408 trunk build and 2002041618 RC1 branch in OS9.x.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Here is a stacktrace of the hang. Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 3E8EBEF0 06F4C320 PPC 3E8DB638 06F4C2C0 PPC 3E8DAE28 06F4C170 PPC 3E3D7168 NSGetModule+01638 06F4C130 PPC 3D32FC08 NSGetModule+0E558 06F4C0F0 PPC 3D33015C NSGetModule+0EAAC 06F4C0A0 PPC 3D3303E4 NSGetModule+0ED34 06F4C060 PPC 3F66C990 Repeater::DoRepeaters(const EventRecord&)+00030 06F4C020 PPC 3D31F7DC 06F4BFE0 PPC 3D31F8B8 06F4BF90 PPC 3D408318 NS_NewAdapterEnumerator+00CE8 06F4BF40 PPC 3D4495B8 PL_ProcessPendingEvents+00088 06F4BF00 PPC 3D4496DC PL_HandleEvent+0001C 06F4BEC0 PPC 3D2532BC NSGetModule+3922C 06F4BE80 PPC 3D24869C NSGetModule+2E60C 06F4BE30 PPC 3C25FBB4 NSGetModule+1E194 06F4BDD0 PPC 3C23B5C8 06F4BD20 PPC 3C237D60 06F4BC80 PPC 3C237754 06F4BC30 PPC 3C25FB14 NSGetModule+1E0F4 06F4BBE0 PPC 3D20B224 06F4BB80 PPC 3E64B944 PR_Write+00014 06F4BB40 PPC 3E6496F8 PR_SetThreadDumpProc+00188 06F4BB00 PPC 3E6461E4 PR_GetConnectStatus+00654 06F4BAC0 PPC 3E64614C PR_GetConnectStatus+005BC
Keywords: regression
changing target milestone from 9.xx to 1.0.
Target Milestone: mozilla0.9.1 → mozilla1.0
nomianitng for nsbeta1, because it is a hang that has been reopened, that has been marked as critical byt th reporter.
Keywords: nsbeta1
Whiteboard: [adt3 RTM]
Target Milestone: mozilla1.0 → ---
I can report that this is again WFM in recent 1.1a builds. 2002062210 trunk for MACOS9.
Hirata: please mark RESOLVED/WFM since you had REOPENED.
WFM 2002062508 trunk.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → WORKSFORME
VERIFIED: per reopening contributor.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.