User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020904 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020904 After viewing any more than 5 pages with an embedded flash animation, Mozilla will choke and die. This always happens. Unfortunately, it sometimes manages to totally obliterate the bookmarks file after this crash happens. This has happened to me twice so far. Reproducible: Sometimes Steps to Reproduce: My best guess on how to reproduce a problem would be: 1. Go to a page with a flash animation (try homestarrunner.com) 2. Bookmark the page. 3. Continue browsing the pages with the flash animations until Mozilla keels over. 4. Restart Mozilla and check bookmarks. Actual Results: Mozilla died, and bookmarks were reset to defaults upon restarting. Expected Results: Not crash, and leave the bookmarks alone.

are you running on a remote display (that would explain the crash at least, bug 58937)?

No, this is a local display. How does one enable TalkBack in the recent builds?

Interestingly enough, I discovered bug 98476 which seems to reference this problem in the first comment. While the bug itself is requesting a redundancy feature added to recover prefs.js and bookmarks.html, the original commenter mentions the random nuking of bookmarks.html after a crash. That bug has been marked as FIXED. However, this does appear to still be an issue.

talkback should be enabled in the .tar.gz builds from .mozilla.org. When you crash, it should come up and allow you to send the report in. If talkback doesn't pick up the crash, try running Mozilla from a terminal and see if it at least prints an error message in your terminal when it crashes. see also bug 131105: "crash causes loss of bookmarks added during current session" (note that the crash with flash and losing the bookmarks are separate bugs)

The bookmarks getting reset problem is bug 164244. As far as the Flash crash, there's not much we can do without a talkback id and some definite reproducible steps. If you can provide this information, I suggest opening a new bug. Thanks. *** This bug has been marked as a duplicate of 164244 ***