Firefox Developer Edition crashes because of older Firefox OS simulator

RESOLVED INCOMPLETE

Status

()

Firefox
Developer Tools
RESOLVED INCOMPLETE
4 years ago
4 years ago

People

(Reporter: ifilin, Unassigned)

Tracking

35 Branch
All
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
I ran Firefox Developer Edition v35.0a2 (linux) in the following settings:
1. 64bit version on OpenSUSE 13.1(64bit)
2. 32bit version in Linux emulation on NetBSD 7(64bit)

In both cases, due to Firefox OS 1.1 Simulator that was still being synced through my sync account, the browser crashed (NetBSD Linux emulation) or just became unresponsive and I had to kill it (OpenSUSE). 

The crash always happened when I was opening a new tab, after the browser started normally. A message about incompatibility with Firefox OS Simulator would show up on the new tab, but then the browser would crash or just become unresponsive.

The fix was easy though, I went to my regular Firefox and removed Firefox Simulator from my Add-Ons and waited for this to be synced.
On netbsd I deleted my ~/.mozilla/firefox folder, restarted Firefox Developer Edition and synced it again.

Unfortunately, in both cases no crash dumps were generated and the crash reporter did not come up.

Other than that I haven't experienced any problems. 
Great job on this version of Firefox!
Ryan, could this be related to the recent IndexDB changes? Although I don't think this report is actionable to be honest.
Firefox OS Simulator 1.1 is no longer maintained.  Even then, we would need more details like a log to be able to investigate this unfortunately.

You can use WebIDE to install simulators for Firefox OS 1.2+.

(In reply to Panos Astithas [:past] (overloaded, please needinfo) from comment #1)
> Ryan, could this be related to the recent IndexDB changes? Although I don't
> think this report is actionable to be honest.

I don't think so, but I agree it's hard to say.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.