Starting this morning, Chrome Canary (Version 68.0.3410.0) has been crashing to desktop pretty regularly and showing the following message when it's started back up.
I know that Chrome Canary is bleeding edge software, but I wanted to bring this up now, in case this starts happening in the future with the stable Chrome branch.I've checked in Event Viewer but there are no error messages related to either Groupy or Chrome Canary after each crash. I've tried toggling off the "allow processes to run in the background" option in Chrome Canary, but that didn't fix the issue. I've got an install of the stable version of Chrome, so this isn't a huge deal, but I figured I'd bring it up anyway. If any more info is needed, feel free to ask for it.
Specs:
Windows 10 Pro x64Intel i7-7700K16 GB G.Skill DDR4 3200GTX 1080 Ti SLIGroupy is installed on the same SSD as both Windows and Chrome Canary
Try a Purge first https://forums.stardock.com/488142/groupy-support-faq#reinstalling
reboot and reinstall , then report back here , please
Did the purge and then reinstalled. Crash still occurs with the same tab opening up afterwards saying to remove Groupy.Edit: It's odd, because I'd been using Chrome Canary for a few days with Groupy installed and it was all working fine. It just started happening today, so I'm thinking maybe Chrome Canary updated and that caused a conflict of some sort.
I have chrome ( not that version ) with no Groupy problem so it might be that version
is your problem.
I'll forward this to support and see if they have a known solution , so check back here .
Will do. Thanks.
I found a soluction. Enable all the experimental Material Design in chrome://flags. Solve this problem. Only the taskbar titles not.
enable the following Flags. Remember to Relaunch the browser everytime you enable a flag.
Thanks. I'll give it a shot and report back.
Well, it's been almost 3 hours without a crash, when before it was crashing within 10 minutes of opening up Chrome. So far, so good. Thanks for the advice.
Unfortunately without a call stack from the crash or a reproducible test case there is little we can do.
Because chrome catches its own crashes I don't think it logs them in the event log which makes it even harder to track down crashes in the field.
Actually scrub that, apparently it stores dmp files here : %HOMEPATH%\AppData\Local\Google\Chrome\User Data\Crashpad\reports
There should be some dmp files from the crashes here. It would be much appreciated if you could upload them so we can take a look.
the problem isn't with Groupy. is with canary last update. stay free
Any of you happen to see trouble with this current version of Canary 70.0.3530.0 ?
Groupy 1.17 was making nice groups in Canary for me until about a week ago then now I can not make Canary group at all...
no crash issue, Canary just behaves like it is excluded in some way...
regular chrome and other applications are still grouping just fine on the same machine (windows 10 current version on the 'slow = business' update channel)...
fyi...Groupy 1.17 working ok again with Canary 70.0.3534.0...looks like 3530 had disrupted Groupy in some way...
Long term unfortunately Chrome will not be groupable once Google block the loading of third party code. If we are blocked we will simply prevent grouping of that process. Complaints regarding that would need to go to the chrome developers.
It could well be that's the problem for you there.
Hi Neil, thanks for the heads up...ugh...guess now I know that I do like using Groupy...lol...so far Canary has definitely stopped grouping for me in all builds after 3534...
There are many great features available to you once you register, including:
Sign in or Create Account
