User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:126.96.36.199) Gecko/2009072213 Firefox/3.0.12 Build Identifier: Firefox/3.5.2 downloaded from http://www.mozilla.org/ports/os2/ The first time I started Firefox 3.5.2, my system locked up and I had to reboot. The second time I started it, I was able to open the home page and one other page, then when I tried to access another page, Firefox crashed. I've reverted to using FF 3.0. Reproducible: Sometimes Steps to Reproduce: 1. Start Firefox 3.5.2 2. Access any page 3. access any other page Actual Results: First time, system locked. Second time, FF crashed. Expected Results: FF should have opened and stayed open until I closed it. I'm using eComStation 1.1 and had a couple older DOS programs open when I opened FF the first time. When I opened it the second time, only my firewall and some basic processes were running.
As it works for mostly everybody else, it has to be something specific on your machine, although at the moment I can't even guess what it could be. Some starting points for an investigation: - Do you have something related to these crashes in POPUPLOG.OS2 on your bootdrive? - If you start FF 3.5.2 from the command line like this firefox.exe > output.log 2>&1 does output.log contain something? - If you start it in safe mode, disabling all add-ons (using the -safe-mode parameter) does it still crash? If so, what extensions and plugins are you using? (I hope this doesn't cause any more system locks!)
Version: unspecified → 3.5 Branch
You may need to create a new profile as well. I don't believe Firefox can cause system freezes on Mac (I know it can't on windows), but not sure. What is your crash about? Do you have a stack trace? http://support.mozilla.com/kb/Profiles https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
Tyler, we don't have such stack traces on OS/2. And badly written apps can indeed lock the PM interface of OS/2 so that the system appears to be locked (I just haven't seen that happening with Mozilla apps for a long time).
Not enough information to start an investigation.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.