Closed
Bug 6743
Opened 26 years ago
Closed 26 years ago
[PP] Mac only - crash running Profile Wizard
Categories
(SeaMonkey :: Installer, defect, P1)
Tracking
(Not tracked)
M6
People
(Reporter: pmock, Assigned: racham)
Details
Build:
Mac May 19 Seamonkey build (1999051909) running on PPC 8500/180 OS 8.5.1
Problem:
Mac Only. You crash when you click on the "Finish" button running the Profile
wizard. You can continue on by copying your prefs50.js into the new profile
directory that was created by the wizard and restarting Apprunner.
Note: this problem does not occurs on Win32 or Linux May 19 builds.
Steps to reproduce problem:
0) Remove your Mozilla Registry from the Your_HD:System Folder:Preferences
folder.
1) Run Apprunner
The Communicator Profile Manager dialog appears
2) Click on the Next button
3) Enter in a Profile name
(Leave the 2nd field blank)
4) Click on the Next button
5) Enter in your Full Name and your email address
6) Click on the Next button
7) Enter in your outgoing SMTP mail server name
8) Click on the Finish button
Crash to Macsbug
I was running the Mozilla build, so there was no talkback log.
MacsBug log
-----------
The ÒapprunnerÓ heap at 02025C70 is ok
Totaling the ÒapprunnerÓ heap at 02025C70
Total Blocks Total of Block Sizes
Free 0032 #50 0022A7E0 #2271200
Nonrelocatable 00AA #170 00716F7C #7434108
Relocatable 01D6 #470 00050F60 #331616
Locked 0005 #5 00049540 #300352
Purgeable and not locked 0000 #0 00000000 C 068B02F4
nsComponentManagerImpl::Init()+001B4
02BAE680 PPC 068AFC04 nsRegistryFactory::CreateInstance(nsISupports*,
const nsID&, voi
d**)+0005C
02BAE630 PPC 068AD91C nsRegistry::nsRegistry()+0005C
02BAE5F0 PPC 0689B2C8 NR_StartupRegistry+0008C
02BAE5A0 PPC 06899288 nr_RegClose+000AC
02BAE550 PPC 068977EC nr_Unlock+0002C
02BAE510 PPC 06897210 nr_UnlockRange+0000C
PowerPC illegal instruction at 00020004
UªMacMessagePump::DoMouseUp(EventRecord&)+0004C
02A03E70 PPC 05DDD028
nsMacMessagePump::DispatchOSEventToRaptor(EventRecord&, GrafPort
*)+00044
02A03E20 PPC 05DD72AC nsMacMessageSink::DispatchOSEvent(EventRecord&,
GrafPort*)+00038
02A03DE0 PPC 05DD2DCC nsMacWindow::HandleOSEvent(EventRecord&)+00020
02A03D80 PPC 05DD31EC
nsMacEventHandler::HandleOSEvent(EventRecord&)+0009C
02A03D40 PPC 05DD4288
nsMacEventHandler::HandleMouseUpEvent(EventRecord&)+000AC
02A03CC0 PPC 05DBD8E8 nsWindow::DispatchMouseEvent(nsMouseEvent&)+00058
02A03C60 PPC 05DBD830 nsWindow::DispatchWindowEvent(nsGUIEvent&)+00018
02A03C20 PPC 05DBD75C nsWindow::DispatchEvent(nsGUIEvent*,
nsEventStatus&)+00090
02A03BD0 PPC 060A2C28 HandleEvent(nsGUIEvent*)+00058
02A03B80 PPC 060A04F0 nsViewManager::DispatchEvent(nsGUIEvent*,
nsEventStatus&)+005C4
02A03A40 PPC 060A46F8 nsView::HandleEvent(nsGUIEvent*, unsigned int,
nsEventStatus&)+0
0134
02A039C0 PPC 060A46F8 nsView::HandleEvent(nsGUIEvent*, unsigned int,
nsEventStatus&)+0
0134
02A03940 PPC 060A46F8 nsView::HandleEvent(nsGUIEvent*, unsigned int,
nsEventStatus&)+0
0134
02A038C0 PPC 060A4770 nsView::HandleEvent(nsGUIEvent*, unsigned int,
nsEventStatus&)+0
01AC
02A03840 PPC 061BFDBC PresShell::HandleEvent(nsIView*, nsGUIEvent*,
nsEventStatus&)+00
220
02A037C0 PPC 062405D8
nsEventStateManager::PostHandleEvent(nsIPresContext&, nsGUIEvent
*, nsIFrame*, nsEventStatus&, nsIView*)+001BC
02A036F0 PPC 06241130
nsEventStateManager::CheckForAndDispatchClick(nsIPresContext&, n
sMouseEvent*, nsEventStatus&)+001F0
02A03650 PPC 062770C0
nsHTMLButtonElement::HandleDOMEvent(nsIPresContext&, nsEvent*, n
sIDOMEvent**, unsigned int, nsEventStatus&)+00024
02A034F0 PPC 063993B8 nsGenericElement::HandleDOMEvent(nsIPresContext&,
nsEvent*, nsID
OMEvent**, unsigned int, nsEventStatus&)+000DC
02A03490 PPC 0623ECE0
nsEventListenerManager::HandleEvent(nsIPresContext&, nsEvent*, n
sIDOMEvent**, unsigned int, nsEventStatus&)+00330
02A03390 PPC 06723A4C nsJSEventListener::HandleEvent(nsIDOMEvent*)+00190
02A032F0 PPC 067B038C JS_CallFunctionValue+00014
02A032B0 PPC 067C8B9C js_CallFunctionValue+000B8
02A03200 PPC 067C899C js_Invoke+0057C
02A03120 PPC 067CEB38 js_Interpret+05900
02A02EE0 PPC 067C899C js_Invoke+0057C
02A02E00 PPC 067CEB6C js_Interpret+05934
02A02BC0 PPC 067B5550 js_GetAtom+0005C
02A02B70 PPC 067B0AD0 JS_ReportErrorNumber+00038
02A02B30 PPC 067B6734 js_ReportErrorNumberVA+0014C
02A02AA0 PPC 067B6828 js_ReportErrorAgain+0002C
Closing log
Updated•26 years ago
|
Assignee: sgehani → racham
Comment 1•26 years ago
|
||
Profile wizard issue: reassigning to Bhuvan.
I downloaded the commercial build, Mac May 19 1999051909 build, and was able to
get talkback logs. Note: the MacsBug logs generated from this build is similar
to the ones generated from running the mozilla builds.
Tracking ids: ESM59ILA and ESN07EEA
Stack Trace
-----------
Trigger Reason: PowerPC unmapped memory exception
Call Stack: (Signature = NSStdLib + 0x2b848 (0x0695c3e8) f41e65e7)
NSStdLib + 0x2b848 (0x0695c3e8)
JavaScript + 0xbf18 (0x067b4828)
JavaScript + 0xbe24 (0x067b4734)
JavaScript + 0x61c0 (0x067aead0)
JavaScript + 0xac40 (0x067b3550)
JavaScript + 0x2425c (0x067ccb6c)
JavaScript + 0x1e08c (0x067c699c)
JavaScript + 0x24228 (0x067ccb38)
JavaScript + 0x1e08c (0x067c699c)
JavaScript + 0x1e28c (0x067c6b9c)
Updated•26 years ago
|
Severity: major → blocker
Priority: P3 → P1
Product: MailNews → Browser
Comment 3•26 years ago
|
||
This happens on windows as well as mac, at least the first time you run the
profile manager
Comment 4•26 years ago
|
||
On Unix, it does not appear to actually crash, but you must re-launch after you
are done with the profile manager. If you would like a separate bug on this
please let me know.
On Windows, you crash the after closing the profile manager on a clean install.
The talkback incident ID is 8823763
Call Stack: (Signature = js_Invoke 9bd55ef4)
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 698]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2200]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 671]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2200]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 671]
js_Interpret
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2200]
js_Invoke
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 671]
js_CallFunctionValue
[d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 736]
JS_CallFunctionValue
[d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 2439]
nsJSEventListener::HandleEvent
[d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 98]
nsEventListenerManager::HandleEvent
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line
565]
nsGenericElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\layout\base\src\nsGenericElement.cpp, line 770]
nsHTMLButtonElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\layout\html\content\src\nsHTMLButtonElement.cpp,
line 375]
nsEventStateManager::CheckForAndDispatchClick
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line
578]
nsEventStateManager::PostHandleEvent
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line
169]
PresShell::HandleEvent
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2020]
RAPTORVIEW.DLL + 0x1d4a (0x01981d4a)
RAPTORVIEW.DLL + 0x1d10 (0x01981d10)
RAPTORVIEW.DLL + 0x1d10 (0x01981d10)
RAPTORVIEW.DLL + 0x1d10 (0x01981d10)
RAPTORVIEW.DLL + 0x635d (0x0198635d)
RAPTORVIEW.DLL + 0x23f0 (0x019823f0)
RAPTORWIDGET.DLL + 0x5ed0 (0x00fc5ed0)
RAPTORWIDGET.DLL + 0x5f16 (0x00fc5f16)
RAPTORWIDGET.DLL + 0x80cc (0x00fc80cc)
RAPTORWIDGET.DLL + 0x82f8 (0x00fc82f8)
RAPTORWIDGET.DLL + 0x79b5 (0x00fc79b5)
RAPTORWIDGET.DLL + 0x5fa0 (0x00fc5fa0)
KERNEL32.DLL + 0x3663 (0xbff73663)
KERNEL32.DLL + 0x22894 (0xbff92894)
0x00788c40
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
This is happening because of CloseWindow() call of toolkitCore.
There is bug filed on this already i.e., to fix that call which would
get rid of this problem. I think this problem is seen on Windows and Mac.
Marking this as duplicate of bug 6005.
*** This bug has been marked as a duplicate of 6005 ***
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•