Closed
Bug 196970
Opened 23 years ago
Closed 23 years ago
[MachO] crash when using existing profile
Categories
(Core :: Preferences: Backend, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 196337
People
(Reporter: mozilla, Assigned: ccarlen)
Details
since trunk build 2003-03-07 Mozilla has crashed when stated using any of my
excisting profiles. Mozilla doesn't crash when using a newly created profile.
This is *not* a problem with the two 1.3 release candidates.
TalkBacks : TB188513W , 514M , 522X , 556Q , 573E plus a few using later builds.
It seems to be a regression issue in the trunk builds, as 2003-03-06 and the two
release candidates don't show this behaviour.
| Reporter | ||
Updated•23 years ago
|
Severity: normal → critical
Comment 1•23 years ago
|
||
Is it possible that you attach (via create new attachment) a OS X crash log of
that crash ?
It's faster than asking someone at NSCP for the TB stack...
| Reporter | ||
Comment 2•23 years ago
|
||
Even better :-)
I've isolated the problem to be this preference:
user_pref("nglayout.debug.disable_xul_cache", false);
Even a prefs.js containing *only* this line will crash Mozilla 2003-03-07 and
forward
Comment 3•23 years ago
|
||
*** This bug has been marked as a duplicate of 190358 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•23 years ago
|
Summary: [MachO] crash when using excisting profile → [MachO] crash when using existing profile
Comment 4•23 years ago
|
||
er, no dupe ...
That shouldn't crash Mozilla if the pref is renamed...
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 5•23 years ago
|
||
Should be fixed in tomorrow's build.
*** This bug has been marked as a duplicate of 196337 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•