Closed Bug 767075 Opened 12 years ago Closed 3 years ago

[adbe 3290789] Firefox 13.0 freezes on Windows Server 2008 / 2012 RP with protected mode enabled in Flash 11.3

Categories

(Core Graveyard :: Plug-ins, defect)

13 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: glen, Unassigned)

References

Details

(Whiteboard: [flash-11.3])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0
Build ID: 20120601045813

Steps to reproduce:

have Windows 2008 server, standalone, not on domain. Firefox 13.0 installed (also tried 13.0.1). When logged into main console firefox opens and works fine. When I log into terminal session on this server and open firefox, Firefox opens but several seconds after opening it will hang and says "not responding". Removed, reinstalled, removed firefox profiles, removed windows profile, nothing seems to fix. I even ran firefox portable from portableapps.com and it crashes same. I then removed it all and installed older Firefox 11.0 and it works just fine. 


Actual results:

see above.


Expected results:

Firefox should open and work normally under terminal services session.
A hang/freeze (not responding) is no crash....

Does it work in the Firefox safemode ?
http://support.mozilla.org/en-US/kb/Safe+Mode
(that disables the hardware acceleration)
Summary: firefox 13.0 crashes in terminal server → firefox 13.0 freezes in terminal server
Safe mode option does not work. If you run that way, it also hangs with "not responding" after loading for several seconds. All other options do as well.
The only issue that i can imagine is the hardware acceleration but that is disabled in the safemode
Thanks. The issue was with flash. I followed note about adding protectedmode=0 to cfg file and then reinstalled 13.0.1 and it works fine. I found flash install log file that showed it was updated on 16th which was when the problem started. I think it is very odd that it works in main console but not in terminal services, but at least it is fixed. Thanks for the help.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Component: Untriaged → Plug-ins
Product: Firefox → Core
QA Contact: untriaged → plugins
Glen, can you please file a bug with Adobe about the specific issue with freezes using terminal server? That may not be a configuration that they have tested and we need to make sure they are aware of it.
ok.
Whiteboard: [flash-11.3]
Summary: firefox 13.0 freezes in terminal server → Firefox 13.0 freezes in Windows Server 2008 terminal with protected mode enabled in Flash 11.3
I'm also seeing this exact same issue on Windows Server 2012 RP with Firefox Nightly 17.0a1 (2012-07-19) and Flash 11.3.300.265, but I'm physically at the machine and not using Terminal Services. Anytime I browse to a page that has Flash (even Gmail), Firefox hangs. No crash.  It hangs until I kill the plugin container a few times and the plugin container doesn't start back up (doesn't always work). I also tried the new Flash 11.4 beta, but the result was the same.

Event logs seem to be pointing to a Flash crash followed by an ATIeRecord (ATI EEU Client event error).

Flash seems to be working fine on IE 10.0 and Chrome 22.

See my original post here:
http://forums.mozillazine.org/viewtopic.php?f=23&t=2504549
I reopen this bug because it seems to be specific to OS Windows Server.
Maybe someone from Adobe will tell us if this OS plateform have been beta-tested and if the issue is known.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
We're investigating this bug.  The public Adobe bug number is 3290789.
Summary: Firefox 13.0 freezes in Windows Server 2008 terminal with protected mode enabled in Flash 11.3 → [adbe 3290789] Firefox 13.0 freezes on Windows Server 2008 / 2012 RP with protected mode enabled in Flash 11.3
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: REOPENED → RESOLVED
Closed: 12 years ago3 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.