74312 - Certain Preference Panels Still Crash App on "OK"

Status: VERIFIED DUPLICATE of bug 68208

(SeaMonkey :: Preferences, defect)

Description

[dan.m]

While it seems in most cases I can change preferences to one area (while a page
is open in the browser window) and then click OK to accept them, if I change the
preferences in multiple areas, clicking OK results in a crash. This seems
particularly true when altering settings in the "Navigator" and "Advanced"
areas. When I change multitple settings in these areas and click OK, I get a
crash almost every time. Same was true in Mozilla .8

Comment 1

[sairuh (rarely reading bugmail)]

dmoughamian, could you pls provide us with specific steps to reproduce this bug?
also, does talkback [trace reporting app for crashes] come up for you when this
occurs [need make sure talkback is installed, tho']?

thanks!

Comment 2

[dan.m]

OK...here's the cause of this as far as I can tell. Upon further investigation, it is NOT the changing of multiple 
preferences in the Navigator and Advanced areas, but rather the changing of the font size and resolution 
preferences. As I went through (the first time around), I didn't make note of the fact that BEFORE I went to 
change the other preferences in Navigator and Advanced, I changed the two font size drop-down menu 
values, and I also changed the resolution setting from 96 dpi to 72 (Mac)...this is what seems to crash the 
browser. Because now, if I do change JUST the Font values, the browser still crashes. If I change the 
Navigator and Advanced preferences WITHOUT changing the Font prefs, nothing happens. Sorry for the 
confustion.

No talk-back on the build I downloaded, apparently. Usually just came up automatically on a crash. Hasn't 
happened this time around.

Comment 3

[sairuh (rarely reading bugmail)]

ah, crashing while modifying font prefs! i bet this is bug 68208.

*** This bug has been marked as a duplicate of 68208 ***

Comment 4

[sairuh (rarely reading bugmail)]

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.