Another update: so explorer.exe no longer crashes in the normal sense, but it is hanging intermittently in a way that forces me to restart the process via taskmanager. It only happens when I have multiple instances of explorer running for a sustained period of time, and then one or more of the instances will appear to minimize and flash repeatedly until I restart the process. Here's an example of what that looks like: <img src="https://cdn.stardock.us/forums/47/90/4790495/e9094fc6-c98
istari101
[quote who="Neil Banfield" reply="16" id="3706768"] That's odd as tab bar expanding to full width is purely a visual thing. A colour painted Vs transparency. [/quote] That's even stranger then. Tuning off the expanding tab bar option definitely fixed the perma-minimized issue though, so I'm at a loss on that one. If I have time this coming week I'll try enabling/disabling it again to see if it was just a fluke.
[quote who="Neil Banfield" reply="13" id="3706754"] One additional question, are people using combine tabs with titlebar or tabs above titlebar? [/quote] My tabs are set to "always place above." I also have "tab bar should extend to full window width" disabled because it caused super buggy behavior and focus issues with the Chrome windows I have up. Edited to add: "super buggy behavior" with full window width enabled meant that Chrome windows were being permanently s
[quote who="Neil Banfield" reply="10" id="3706623"] Are any of you technical enough to provide crash dumps from explorer when it crashes as we have had no luck reproducing here and that would pinpoint the exact location things were going wrong. [/quote] The v1.1 update seems to have solved the consistent explorer.exe crash issue for me -- huzzah! -- but I'll check the event log and try to harvest any crash dump that Windows generates if it happens again. I stil
Another issue to report: When trying to move a tab around inside a Grouped instance of Chrome, that tab will *sometimes* bug out and seem to come "unstuck," flashing several times before either disappearing or winding up inside a completely different or new instance of Chrome. It's really hard to track visually when it happens, but I have not yet found any particular set of circumstances that reliably cause this. It also happens whether Chrome is set to auto-Group, never auto-Gro
[quote who="Neil Banfield" reply="3" id="3699865"] Thank you for the feedback. We will investigate further to see if we can see whats causing this. [/quote] Thanks! :)
Opening or interacting with the recycling bin seems to trigger it more than almost anything else at this point, although I don't have a ton of data points after less than a week.
Hello! I'm less than a week into my 30-day trial of Groupy and am really likin