Ever since the introduction of next I've had this issue where everything crashes (both on worklet and booster) if the window/tab is not in foreground.
Once the window loses focus, i.e if another tab is selected or the window gets minimized the app will immediately stop responding.
As long as next is visible on the screen it stays alive, so if I want to work in probe while a next is open I usually just open probe on my second monitor.
This is not exactly ideal but I've learned to live with it, the issue is now that if I press "Bounce Timeline", a new tab is automatically opened making everything crash.
All [.audiotool.com/] tabs will stop responding (except the board for some reason?) the second the app loses focus.
The following part is no longer true and does not work reliably! I managed to do it once earlier today, but after writing it I tested again and could not get it to happen with worklet or booster.
- "To mitigate this before a fix is implemented, you can open an instance of probe in split screen mode or on a different monitor (as long as they are both in view and not overlapping). Pressing bounce will then use the open instance of probe instead of opening a new tab in the current window and everything will work as intended.* "
crash example: https://drive.google.com/open?id=1Y2Uvi1RKmWhJ8SFUS2Or7L0zFsOBP0uv
Comments (11)
Hi, I tried that now, in short it made no real difference and problem still persists.
Here's what I found.
In regards to popups, it seems uBlock Origin does it's job a little too well when paired with the optional uBlock companion extension which works as "A companion extension to uBlock Origin: to gain ability to foil early hostile anti-user mechanisms working around content blockers."
In incognito mode I still had uBlock Origin enabled, but not the companion extension. The anti-adblocker parts of the uBlock companion actually prevents the "Deactivate popup-blocker" warning from showing up!
So when I tried in incognito mode I did get the warning, I then went to disable uBlock from running in Incognito (I like to block ads in incognito too). After disabling uBlock, I still got the warning, and then noticed in the address bar, a little icon telling me Chrome has blocked audiotool from showing popups.
Lastly, I gave audiotool permission to show popups by clicking allow popups in the menu that came up when I clicked the button in the address bar.
Despite all this effort, probe still opens in a new tab, and everything still does unfortunately crash.
Is probe supposed to open as a new window by default?
yes, it freezes no matter what. Once it loses focus the tabs stop responding.
The dev tools, does not work once the tab has crashed. If I try to open dev tools while the tab is hanging, it shows no resources and no warnings, it's like it has not loaded in yet.
Closing the tab is also very difficult when this happens, often taking up to half a minute after initially pressing the button. With dev tools open, I got a myriad of errors, for a couple of milliseconds while the tab was closing. I'll try to catch them on video.
oh boy, I think I have some results. Uploading video.
Started recording a bit after it crashed, this time I opened the dev tools before the crash so it would already be loaded in. As you can see, the tab took around 2 minutes before closing.
In short this gets spammed forever until tab is closed:
[Violation: Message handler took (a long time) to respond]
https://drive.google.com/file/d/1PX3ySoT2O8G_7VUB85D_8YUF54bj4Fez/view?usp=sharing
that sounds great!
oh okay, the app is in it's crashed state here. It doesn't always completely black out but it is unresponsive in the same way. I am getting no other errors while it is hanging like that.
No worries, I appreciate the help :)
If you need me to do more in depth debugging let me know and I'll try my best.
I can still use the app so this is not critical as of now :)
I have a fix for this. Hang on a minute.
https://www.audiotool.com/board/newbie/fix_for_freezing_project
Is this still an issue?