Closed Bug 226166 Opened 22 years ago Closed 21 years ago

Browser will hang when switching to a profile which does not configure proxy correctly

Categories

(SeaMonkey :: General, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: leon.sha, Assigned: blizzard)

Details

Make sure you are using GTK2 built mozilla. 1.start browser with default profile, and configure the proxy correctly so that we can browse the web. 2.create another profile, such as "test",with wrong proxy setting and the home page is set as defaultly, mozilla.org. 3.choose Tools->switch profile.., select the "test" profile and double click. 4.The browser will restart and change to the "test" profile and a dialog will jump out saying"www.mozilla.org can not be found....", and the browser is frozen. 5.It is found that this case will reproduce most of the times.
Another testcase for this bug which will occur 100% time. 1. start browser with default profile, and configure the homepage to "abb:" and set the starup page as homepage. 2. switch to another profile. 3. switch back. You will see the dialog: abb is not a registered protocl. 4. Mozilla hang. If mozilla did not hang, try again.
Component: GFX: Gtk → Browser-General
OS: Linux → All
Summary: [gtk2]Browser will hang when switching to a profile which does not configure proxy correctly → Browser will hang when switching to a profile which does not configure proxy correctly
I can repro the case in comment 1 without switching profiles. After step 1, quit Mozilla. Now, launch again. I get the dialog with "abb is not a registered protocol" and the app is hung. Here's the interesting part: if I switch to another app, then bring Mozilla back to the foreground, I can click OK and it's no longer hung. This is on OS X. I'd be curious to know if the switch out and back condition occurs on other platforms.
>###!!! ASSERTION: expected a XUL document: 'xuldoc', file >nsXULContentBuilder.cpp, line 1502 >Break: at file nsXULContentBuilder.cpp, line 1502 I see this in my terminal. Is this the problem?
This bug disappers on mozilla 1.7. So suggest closed it.
Product: Browser → Seamonkey
This bug is gone in trunk.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.