Even if you rip out the code to auto-register components and rebuild the interface manifest, mozilla/viewer will crash if the filesystem is not writable. The reason for this is that the code in reg.c attempts to open the registry as read/write, and then attempts to do the right thing if the open fails with an access error by attempting a read-only open. The only problem is that the case statement attempts to explicitly catch each type of failure but doesn't consider the nspr wrapped EROFS error for read-only filesystem. I will be attaching a patch.

adding crash keyword

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

My apologies, marked this too soon. Reopening.

dveditz, I see your name on all the recent check-ins to reg.c. Will you review my patch?

Looks ok to me, r=dveditz We really need to change the API so it takes a flag on whether read-only is OK or if writing is required. That change would have to percolate all the way up through nsIRegistry and into all client users so it's a bit outside the scope of what we can tackle right now.

patch checked in.

please verify

Marking Verified. Please reopen if problem reoccurs.