1143503 - Crash on startup if xulstore.json is missing from profile

Status: RESOLVED DUPLICATE of bug 1092810

(SeaMonkey :: Startup & Profiles, defect)

Description

[Mark]

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33
Build ID: 20150308222025

Steps to reproduce:

After upgrading from SeaMonkey 2.26.1 to 2.33, SeaMonkey was crashing on every start. It would prompt for the master password; after cancelling that (since I didn't need to use stored passwords at the time) it would crash. Two such crash reports:
http://crash-stats.mozilla.com/report/index/bp-e5f48aaf-55ca-4c09-8a65-fad912150315
https://crash-stats.mozilla.com/report/index/eb85a4b5-76cf-4b82-99a4-7e6922150315

A fresh profile worked. I eventually tracked the crash down to an xulstore.json file not being present in the existing profile (from SeaMonkey 2.26.1), but it was in the fresh profile. After creating an empty xulstore.json file in the profile folder, SeaMonkey 2.33 started OK.

Since creating an empty file is enough to fix the problem, it would seem reasonable to expect that SeaMonkey could do that automatically on startup if the file doesn't exist. Or, since xulstore.json replaces localstore.rdf, it would be even better if settings from the latter (if present) were ported to the new format.

OS is Windows Vista, 32-bit.


Actual results:

Crash on startup.


Expected results:

If xulstore.json doesn't exist in the profile, it should be created from localstore.rdf if that exists. Otherwise a default xulstore.json should be created. Certainly should not crash.

Comment 1

[Mark]

It may be relevant that I have two Windows user accounts set up:
- One a standard user account, which I use most of the time.
- The other an administrator account, which I mainly use through UAC - I hardly ever log in to it directly.

To update SeaMonkey, I:
- Ran SeaMonkey 2.26.1 as Administrator.
- Help > Check for Updates.
- Allowed the update.
- Closed SeaMonkey once the update was complete (not using the restart option; I'm never quite sure if that will restart still as administrator or as the standard user).
- Ran SeaMonkey as Administrator; it applied the update.
- After checking extension compatibility, SeaMonkey 2.33 crashed.
- Subsequently running as Administrator was fine - no crash.
- However, running as standard user crashed every time after dismissing the master password prompt; it didn't resolve after the first time like running as Administrator did.

Comment 2

[therube]

DUP of Bug 1092810 - startup Crash after migration data from Seamonkey v.2.30 Final to Seamonkey v2.31 Beta 1 Build 1 [@ nsRDFPropertyTestNode::FilterInstantiations(InstantiationSet&, bool*) const ]