Closed Bug 69085 Opened 24 years ago Closed 24 years ago

Crash when changing font (or size) in prereferences

Categories

(SeaMonkey :: Preferences, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 68208

People

(Reporter: tuschner, Assigned: matt)

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.13 i686; en-US; 0.8) Gecko/20010215 BuildID: 20011503 When I try to change the font type or size in the prerefecense dialog mozilla chrashes right away. Reproducible: Always Steps to Reproduce: menu - edit - prerefereces - font change the font or size
Works for me with 2001021503 0.8 on Slackware 7.0 (glibc 2.1.2/XFree86 3.3.6, no xfs).
Scratch my last comment - crashes after two or three repeated changes in font size. Gives me a SIGSEV; the last part of an strace looks like: gettimeofday({458814, 197135500}, NULL) = 0 gettimeofday({197132413, 197135504}, NULL) = 0 ioctl(8, FIONREAD, [0]) = 0 poll(0x41c32600, 0x3, 0x9, 0x4030b520, 0x41c32600) = 1 ioctl(8, FIONREAD, [40370569]) = 0 read(8, "\n\0\t\0<\1\2\0\220\f\300\v6\1\2"..., 32) = 32 mprotect(0x41e20000, 4096, PROT_READ|PROT_WRITE) = 0 write(6, "}", 1) = 1 --- SIGSEGV (Segmentation fault) ---
Possible dup of bug 68208.
hrm, could you get a build with talkback in it [the non-sea tarball, for linux], and when you reproduce this, let us know what the talkback incident number is? we could check if the trace is the same as bug 68208... it really does sound like the same thing, but it'd be good to confirm.
Keywords: crash
The trace given so far in this bug is from an idle thread and is likely irrelevant to the crash.
Talkback incident ID is TB26477281Q
bruce, thx! the trace is similar, so am gonna dup this one... *** This bug has been marked as a duplicate of 68208 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
mass verification of duplicate bugs: to find all bugspam pertaining to this, set your search string to "DuplicateBugsBelongInZahadum". if you think this particular bug is *not* a duplicate, please provide a compelling reason, as well as check a recent *trunk* build (on the appropriate platform[s]), before reopening.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.