You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried it with three different systems. With the version 3.5.1 everything works well, but with the later versions (I've tried up until the 3.6.1) the Pick-a-Browser window freezes upon choosing between Chrome, Brave, Opera, Epic, Maxthon, etc... The browser window opens with the right url, but the Pick-a-Browser window is still there and has no reaction. What's even stranger is that with Firefox, Firefox Developer Edition and Edge it is still working. Also, if I close the browser window, the Pick-a-browser window closes too and everything runs normal. If I click many times the "Pick-a-Browser" window, or if I try closing it, the app crashes.
Am I doing something wrong here?
Many thanks,
Christian
The text was updated successfully, but these errors were encountered:
It doesnt related to chromium, since for me it happens also with Links browser and MPV. It seems to be that a BrowserTamer waits for process its spawned to end.
If browser is already open at the moment of choosing its works just fine, but if browser is closed, the process spawned by BT becomes main process of the browser and doesnt die immediately
Hello,
I've tried it with three different systems. With the version 3.5.1 everything works well, but with the later versions (I've tried up until the 3.6.1) the Pick-a-Browser window freezes upon choosing between Chrome, Brave, Opera, Epic, Maxthon, etc... The browser window opens with the right url, but the Pick-a-Browser window is still there and has no reaction. What's even stranger is that with Firefox, Firefox Developer Edition and Edge it is still working. Also, if I close the browser window, the Pick-a-browser window closes too and everything runs normal. If I click many times the "Pick-a-Browser" window, or if I try closing it, the app crashes.
Am I doing something wrong here?
Many thanks,
Christian
The text was updated successfully, but these errors were encountered: