Closed
Bug 10420
Opened 26 years ago
Closed 26 years ago
Pref UI setting values
Categories
(SeaMonkey :: Preferences, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M10
People
(Reporter: namachi, Assigned: neeti)
Details
We can easily reproduce this crash. I was able to reproduce this crash wil Jul
22 source tree.
Go To preference.
Change some settings.
Click OK.
It creates assertion which in-turn crashes the browser.
I digged through the source. It seems to be type mismatch in the nshashtable
lookup in the libpref. libpref tries to update the old pref tree with the
new pref and it fails in type mismatch. I deleted the old registery and re-tried
didn't help
Most of the time the following happerns :-
Key value comes out as 128 and Type value comes out as 64 and creates a
assert. or Otherwise.
Updated•26 years ago
|
Assignee: dp → neeti
Namachi,
Could you give me more details about which values you changed, when it crashed.
Thanks,
Neeti
Reporter | ||
Comment 2•26 years ago
|
||
Any value change was crashing.
Shiva
Reporter | ||
Comment 4•26 years ago
|
||
Not testable. Pref listbox is not visible.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
This is most likely a duplicate of another bug whose number escapes me: clicking
rapidly in the prefs window would crash. That problem has since been fixed.
Marking this verified.
Bulk move of all Pref UI component bugs to new Preferences component. Pref UI
component will be deleted.
Component: Pref UI → Preferences
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•