Firefox 13 freezes over remote desktop with hardware acceleration enabled

RESOLVED INCOMPLETE

Status

()

Core
Graphics
RESOLVED INCOMPLETE
6 years ago
a year ago

People

(Reporter: Kris, Unassigned)

Tracking

13 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
Build ID: 20120614114901

Steps to reproduce:

Launched Firefox version 13 (or newer) while running a Windows 7 session over remote desktop with hardware acceleration support enabled (default)


Actual results:

Firefox freezes at launch and must be manually ended.  Disabling hardware acceleration support in Safe Mode fixes this; however, browser will not provide this capability next time it is launch in a local session.  Please add auto-detect capability to temporarily disable hardware acceleration support if a remote session is detected.


Expected results:

Firefox launch as expected
Component: Untriaged → Graphics
Product: Firefox → Core
QA Contact: untriaged → thebes

Comment 1

4 years ago
I think this still happens on Firefox 32.0 on Windows 7.

Comment 2

2 years ago
This bug still happens 4 years later on Firefox 45.0.1 - it was never addressed. Logging in with remote desktop always results in Firefox being 100% frozen and needing to force close.
Please try version 52 when it comes out in March
Flags: needinfo?(deheleri)
Whiteboard: [closeme 2017-04-01]

Comment 4

a year ago
I've frequently experienced a related problem where if I leave Firefox running on a computer and then RDP into that computer, Firefox will then hang and have to be terminated.  This doesn't always happen, it seems likely that it has conditions for the hang to occur (perhaps having used graphics acceleration, ie. watching Youtube video, earlier in the browser session prior to using Remote Desktop).  This occurs even in the latest stable Firefox release (version 52.0.2).  Disabling hardware acceleration in the browser never seemed to be a permanent solution because Firefox would re-enable it (I don't recall if this would happen during browser updates or at some other time).

Comment 5

a year ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Flags: needinfo?(deheleri)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2017-04-01]
You need to log in before you can comment on or make changes to this bug.