880950 - In VMware Workstation + Windows 8, Firfox will get forzen on accessing some pages

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[54yuri]

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; SE 2.X MetaSr 1.0)

Steps to reproduce:

Environment:
1) Worksation 9.x or Fusion 5.x, 
2) Windows 8 Enterprise 32bit or 64bit
3) Firefox 18+
4) granphic card memory > 512mb
5) with or without VM tools
6) DirectX 11


Reproducible:
Always



Steps to Reproduce:
1)  open firefox 
2) access some pages
3) firefox gets forzen, and can not click any element in this page.





Actual results:

Actual Results:
firefox gets forzen, and can not click any element in this page. but the it stil can trigger "mouseover" "mouseenter" "mouseleave" event, but click event is unavailable, so the whole page looks like forzen

Expected Results:
the page should be clickable and trigger any "click" event






Expected results:

Additions:
only in the VMware Workstaion + Windows 8 + FF 18+ will have this issue,

otherwise,
1)  Physical Machine + Windows 8 + FF 18+ 
or 
2)  VMware Workstaion + Windows 7 + FF 18+
or 
3)  VMware Workstaion + Windows 8 + FF 17-

will not trigger this issue.

Comment 1

[Paul Silaghi, QA [:pauly]]

Please check if the issue occurs using Firefox in safe mode (with your addons disabled):
http://support.mozilla.com/kb/Safe+Mode

Or on a new, empty profile:
http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager

Comment 2

[54yuri]

thank you, yes, I have tried "safe mode" and "empty profile", but failed.

looks like it is related to the graphic api from win8 and it is introduced from 18.0

Comment 3

[Paul Silaghi, QA [:pauly]]

This might be a duplicate of bug 686782.

Comment 4

[Bas Schouten (:bas.schouten)]

This should probably be reported to VMWare.

Comment 5

[Justin [:JW_SoftvisionQA]]

I will close this bug due to lack of response by reporter. Also this does sound like a VMWare bug.