Closed Bug 1299499 Opened 5 years ago Closed 5 years ago

Firefox becomes unresponsive if accessing non-remote pages while the RDM is enabled

Categories

(DevTools :: Responsive Design Mode, defect, P1)

51 Branch
defect

Tracking

(firefox48 unaffected, firefox49 unaffected, firefox50 unaffected, firefox51 disabled, firefox52 verified)

VERIFIED FIXED
Iteration:
52.3 - Nov 14
Tracking Status
firefox48 --- unaffected
firefox49 --- unaffected
firefox50 --- unaffected
firefox51 --- disabled
firefox52 --- verified

People

(Reporter: mboldan, Assigned: jryans)

References

Details

(Whiteboard: [multiviewport] [reserve-rdm])

[Affected versions]:
- Firefox 51.0a1 (2016-08-31)
 
[Affected platforms]:
- Windows 10x64, Mac OS X 10.10.5, Ubuntu 16.04x64

[Steps to reproduce]:
1. Launch Firefox.
2. From about:config, enable the devtools.responsive.html.enabled pref.
3. Enable RDM.
4. Open non-remote(Eg. about:config) page the opened tab.
5. Select another tab.
6. Click on the previous tab.

[Expected result]:
- Firefox works correctly.

[Actual result]:
- Firefox becomes unresponsive and in the Browser Console, the Error: Assertion failuretabbrowser.xml:3545:23 is thrown.

[Regression range]:
- I will search for regression ASAP.

[Additional notes]:
- Also, after performing step 4 from STR, the RDM tool is displayed as being enabled in the Developer menu.
QA Whiteboard: [qe-rdm]
Flags: qe-verify+
Priority: -- → P3
Whiteboard: [multiviewport] [triage] → [multiviewport] [reserve-rdm]
Hi :jryans,
Can you help take a look at this bug?
Flags: needinfo?(jryans)
(In reply to Gerry Chang [:gchang] from comment #2)
> Hi :jryans,
> Can you help take a look at this bug?

Yes, we'll get to this as part of our prioritized bug list for this new feature.  I'll remove regression keyword since it confuses tracking for a feature that's not yet enabled.

Is there a specific reason you're calling out this bug, or just because it was marked as a regression?
Flags: needinfo?(jryans)
Keywords: regression
This should be fixed by bug 1296736.
Depends on: 1296736
Assignee: nobody → jryans
Status: NEW → RESOLVED
Closed: 5 years ago
Priority: P3 → P1
Resolution: --- → FIXED
Iteration: --- → 52.3 - Nov 7
The issue is no longer reproducible on Firefox 52.0a1 (2016-10-23).
The tests were performed under Windows 10x64, Mac OS X 10.11.6, Ubuntu 16.04 x64.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.