Closed Bug 65445 Opened 25 years ago Closed 25 years ago

Browser crashes after changing font or size

Categories

(SeaMonkey :: Preferences, defect, P1)

x86
BeOS

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 68208

People

(Reporter: rcorzo, Assigned: ykoehler)

Details

(Keywords: crash, Whiteboard: dup?)

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90) BuildID: 2001011014 Using BeOS 5.03. After going into Edit | Preferences | Fonts if I change the font name or size and press OK, I get a segment violation error: loading symbols segment violation occurred ec7cb471: * 128b movl (%edx), %edx mozilla-bin: Then the browser exits after I dismiss the error dialog. Fortunately, after I restart Mozilla the Preferences show that the font has been successfully changed, despite the previous crash. Reproducible: Always Steps to Reproduce: 1. Open Edit | Preferences | Fonts. 2. Change one of the fonts or sizes. 3. Press the OK button. Actual Results: Segment violation error. Expected Results: Return to browser to view changed font.
might be a dupe. reporter: if possible, could you include a callstack? thanks
Assignee: matt → koehler
Keywords: crash
Here is the requested stack trace: loading symbols segment violation occurred _pl_GetEventCount: _pl_GetEventCount: +0031 ec72a471: * 128b movl (%edx), %edx mozilla-bin:sc frame retaddr fd001934 ec72a4da PL_ProcessPendingEvents + 0000004e fd00194c eca37919 nsAppShell::Run(void) + 00000101 fd001978 ec9a7d78 nsAppShellService::Run(void) + 00000024 fd001988 80009c2b main1(int, char **, nsISupports *) + 00000953 fd001ad8 8000a23b main + 0000011b fd001b04 80006e75 _start + 00000061 mozilla-bin:
sorry, i don't have access to BeOS [fwiw, this is wfm on linux and winNT using 2001.01.16.08]. cc'ing BenB to see if he's seen this...
Keywords: qawanted
the same happens to me using build 2001011701 on BeOS. i haven't done a stack crawl or anything but can if anyone is interested.
confirm based on that. Personaly, I didn't start BeOS since then.
Status: UNCONFIRMED → NEW
Ever confirmed: true
marking self cc
Severity: normal → major
Priority: -- → P1
dupe of 68202 (or vice-versa?)
not sure if this is a dup of bug 68208 --the trace differs. however, am tempted to dup it on the basis of the steps... mcafee, what d'you think?
Whiteboard: dup?
yes dupe of 68208. Stack trace here is from another thread, looks idle. *** This bug has been marked as a duplicate of 68208 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
zap
Status: RESOLVED → VERIFIED
Keywords: qawanted
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.