Issue metadata
Sign in to add a comment
|
Crash while playing a game in fullscreen and ALT+TAB to uses the browser
Reported by
maitre...@gmail.com,
Apr 10 2017
|
||||||||||||||||||||||||
Issue descriptionIMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it. Chrome Version: 57.0.2987.133 Operating System: Windows NT 10.0.14393 URL (if applicable) where crash occurred: Any webpages. It is the browser who entered in conflict with the game. Can you reproduce this crash? Yeah, as much as I want. What steps will reproduce this crash? 1. Launch Google Chrome and ensure that all is cleaned (right-click or open favorites folder or access to settings). 2. Launch a 3D game in fullscreen (in my case, Left 4 Dead 2 with Steam, in 1920x1080 native fullscreen). 3. When in-game, use ALT+TAB to come back to Chrome and do a right-click anywhere or try to open a favorites folder or try to access to settings. The browser will then crash in a few seconds. ****DO NOT CHANGE BELOW THIS LINE**** Crash ID: crash/a7f42a8c80000000
,
Apr 12 2017
Unduping, since we don't have a repro for Issue 708899 and it's bundling a bunch of things, but this is really interesting! Thank you for reporting this issue. That crash does match the pattern for Issue 708899. Our suspicion there is that some third-party software is interfering with Chrome's operation. Specifically %ProgramFiles%\avast software\avast\x64\gaming_spy.dll . There are reports of it interfering with other applications as well - https://us.battle.net/forums/en/overwatch/topic/20752755586 - and some software blocks loading of this dll - https://steamcommunity.com/app/447820/discussions/0/133256758572353818/ I don't think we can block this DLL for users of Chrome in an automated way (users may be relying on the functionality it provides). Ensuring Avast is up-to-date may resolve this problem. There may also be a way to configure Avast so that it does not interfere, but you will need to proceed with caution. If any of these approaches do or do not resolve the issue for you, please let us know. We may be able to find a better solution to this. (also removing view restrictions because I don't think this is exploitable).
,
Apr 12 2017
It would be great if you could disable avast and try the steps again. This should help us isolate if avast is in fact causing problems. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Apr 11 2017Mergedinto: 708899
Status: Duplicate (was: Unconfirmed)