Issue metadata
Sign in to add a comment
|
Unable to launch chrome
Reported by
pmcelre...@gmail.com,
Jan 26 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 Steps to reproduce the problem: 1. Try to launch Chrome 2. See 2 instances of Chrome in Task Manager but no window 3. See 2 instances of Chrome close in Task Manager What is the expected behavior? Chrome launching What went wrong? Chrome just crashes before launching. This happpened with Chrome 54 and was fixed in 55. Crashed report ID: no How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes 55 Chrome version: 56.0.2924.76 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 27 2017
,
Jan 28 2017
Indeed there is a 3rd party antivirus. It is Kaspersky Total Security 17.0.0.611 (c).
,
Jan 29 2017
,
Jan 30 2017
This crash is caused by third-party code "Third party - taskbardockappintegration64.dll" is the relevant magic signature. It seems to be caused by "Bins" by 1UP Industries (http://www.1upindustries.com/bins/Default.aspx).
,
Jan 30 2017
I've sent email to their support alias notifying them.
,
Jan 30 2017
I have tried closing "Bins" and indeed, Chrome now opens. I will also contact their support. Thank you!
,
Jan 30 2017
Closing this out since I don't think there's much we can do beyond contacting the developer.
,
Feb 8 2017
Issue 690149 has been merged into this issue.
,
Feb 8 2017
It works also for me, if quit bins, reported Issue 690149 Thanks
,
Feb 9 2017
I wonder what suddenly caused Chrome to react to bins like this. Chrome seems to be the only application on my PC that has this issue.
,
Feb 9 2017
Bins is doing some sort of hooking into Chrome's browser process. I can't say much more beyond that, as I don't know what it's doing. The developer of Bins should have enough debug information to figure out what he/she needs to fix to stop the crashing, but we have no visibility into it.
,
Feb 9 2017
But its not only bins. It must have been also some context with Kaspersky Internet Security (KIS). I my case, i can also only quit KIS and let bins running, and chrome is working fine again.
,
Feb 9 2017
Interesting. I'll try to dig into what Kaspersky might be doing to interfere. Thanks for the info.
,
Feb 11 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pbomm...@chromium.org
, Jan 27 2017Components: Internals>Installer
Labels: Prestable-56.0.2924.76 M-56