Closed
Bug 10118
Opened 25 years ago
Closed 25 years ago
Crash in preferences
Categories
(SeaMonkey :: Preferences, defect, P2)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M10
People
(Reporter: bratell, Assigned: law)
Details
Overview Description: When accessing the preferences from the menu the browser sometimes crash. If it doesn't then it crashes after switching panels a couple (1-20) times. Steps to Reproduce: 1) Run apprunner.exe 2) Open preferences through the edit menu 3) if it hasn't crashed, try switching panels until it do. Actual Results: A crash with the following stack dump: nsCRT::strlen(const unsigned short * 0x01d5d000) line 261 + 5 bytes nsString::Append(const unsigned short * 0x01d5c788, int 1) line 1017 + 9 bytes nsExpatTokenizer::HandleCharacterData(void * 0x00000000, const char * 0x01d5c788, int 1) line 435 doContent(void * 0x0241f5e0, int 0, const encoding * 0x010c1660 little2_encoding, const char * 0x01d0201a, const char * 0x01d023d8, const char * * 0x0012e004) line 1521 + 35 bytes contentProcessor(void * 0x0241f5e0, const char * 0x01d01b20, const char * 0x01d023d8, const char * * 0x0012e004) line 1028 + 30 bytes doProlog(void * 0x0241f5e0, const encoding * 0x010c1660 little2_encoding, const char * 0x01d01b20, const char * 0x01d023d8, int 29, const char * 0x01d01b20, const char * * 0x0012e004) line 2261 + 21 bytes prologProcessor(void * 0x0241f5e0, const char * 0x01d017a0, const char * 0x01d023d8, const char * * 0x0012e004) line 2132 + 36 bytes prologInitProcessor(void * 0x0241f5e0, const char * 0x01d017a0, const char * 0x01d023d8, const char * * 0x0012e004) line 2121 + 21 bytes XML_Parse(void * 0x0241f5e0, const char * 0x01d017a0, int 3128, int 0) line 852 + 40 bytes nsExpatTokenizer::ParseXMLBuffer(const char * 0x01d017a0, unsigned int 3128, int 0) line 282 + 24 bytes nsExpatTokenizer::ConsumeToken(nsScanner & {...}) line 325 + 18 bytes nsParser::Tokenize(int 0) line 1248 + 21 bytes nsParser::ResumeParse(nsIDTD * 0x00000000, int 0) line 878 + 12 bytes nsParser::OnDataAvailable(nsParser * const 0x0241eda4, nsIURI * 0x023b5600, nsIInputStream * 0x0241c220, unsigned int 1564) line 1153 + 19 bytes nsDocumentBindInfo::OnDataAvailable(nsDocumentBindInfo * const 0x023b75d0, nsIURI * 0x023b5600, nsIInputStream * 0x0241c220, unsigned int 1564) line 2023 + 24 bytes OnDataAvailableProxyEvent::HandleEvent(OnDataAvailableProxyEvent * const 0x0241e2a0) line 634 StreamListenerProxyEvent::HandlePLEvent(PLEvent * 0x0241e2a4) line 473 + 12 bytes PL_HandleEvent(PLEvent * 0x0241e2a4) line 509 + 10 bytes PL_ProcessPendingEvents(PLEventQueue * 0x00c94f60) line 470 + 9 bytes _md_EventReceiverProc(HWND__ * 0xc87f04c0, unsigned int 49389, unsigned int 0, long 13193056) line 932 + 9 bytes USER32! 77e71820() 00c94f60() Expected Results: No crash Build Date & Platform Bug Found: 1999-07-19 debug build from the tree. Windows NT 4.0 SP5, Visual C++ 6 SP3 Additional Builds and Platforms Tested On: None Additional Information: None
Assignee: davidm → law
Component: HTML Dialogs → Pref UI
Priority: P3 → P2
Target Milestone: M9
I've recreated this on my build. Problems is in loading the .xul, not the prefs code itself. I'll look into this close tomorrow.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Target Milestone: M9 → M10
I think this went away. I had prefs working till Necko (and other code) landed, at which time a new bug was opened. I'm closing this as WORKSFORME. If the other Prefs bug is still open (assigned to matt@netscape.com, I believe) then please see if that one can't be used to track the problem).
Bugs 7990 et al talk about similar problems. There is a known issue with multiple clicks in the prefs window crashing the browser. I'm going to go ahead and verify this one to cut down on the number of open bugs; the crashing is covered elsewhere in bugzilla so this problem will be addressed.
Bulk move of all Pref UI component bugs to new Preferences component. Pref UI component will be deleted.
Component: Pref UI → Preferences
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•