286243 - After some crashes main menu, bookmarks, plugins, context menu disappeared

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Miha Psenica]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217

Mozilla has crashed many times - first it was connected to java applets, later
for no reason. After some crashes and systems restarts Mozilla started with all
the plugins inactive (as if they haven't been installed). After a few Mozilla
restarts  main menu (File, Edit,...), bookmarks nad status bar disappeared.
Plugins did not work and right click menu always showed wrong content (a lot of
options, even the ones that weren't usual for that action).

I have run Mozilla 1.8a4 and also with that version the problem persisted. Then
I run Mozilla 1.8b1 again and the problem was (for now) gone.

Reproducible: Didn't try

Comment 1

[Adam Hauner]

Miha: Please, do clean re-install of Mozilla Suite.

Comment 2

[Miha Psenica]

Complete reinstall did not come as an option because I would lose my profile
information (I think).

I have noticed that some of javascript stopped working with this bug
(window.open and .location). I have started to investigate what could be wrong
and have discovered that the problem was in some errors in overlays.rdf in
\chrome\overlayinfo\navigator\content\. I removed a line that would try to load
an extension. I have commented the line and restarted Mozilla and for now
everything seems to work:

<!--RDF:li>chrome://cutemenus/content/cutemenus.xul</RDF:li--> 

I was using Cutemenus 0.3.

Anyway, I think all this should be handeled as exception, that would not fail
the whole application, but just the extension.

Comment 3

[Andrew Schultz]

Miha: extensions act just like any other part of Mozlla, and (as such) they can
crash and/or break things pretty badly.

The current version of CuteMenus is 0.4, but even that might not be compatible
with current trunk (1.8)

Anyway, resolving as INVALID -- this is not a Mozilla bug.  If the problem
reappears, please file a bug with the extension as that's the most likely
location of the problem.