@Devortel
Even that does not work, still getting a crash.
I have created a ticket for this to track: https://github.com/playcanvas/editor/issues/566
Any more data/information you can provide would be very helpful. eg:
- Does it happen on other browsers
- Does it seem to happen with/after a certain project
- Any error messages in logs (if you can get them)
I havenāt had it happen in other browsers, the game is currently struggeling with the other browsers then what Iām normlaly using, so its not thoroughly testet.
I canāt find any real consistency in when its happening. But its only crashing when i press launch, and when the problem has startet not even the playcanvas loading bar will show.
I get no errors in the browser developer tool, if there is another log i donāt know about it.
Another quick add, i still have not had the problem on MacOS, will update if i get it.
Iām going to see if I can reproduce these issue again on my local Mac. Iāve enabled logging so hoping it helps
If you are happy with logging, please use the following: Chrome Browser debug logs - Google Chrome Enterprise Help
Other ideas (if I reproduce this) is to try older version of the PlayCanvas engine and also to try to reproduce on Chrome Canary Chrome Canary features for developers ā Google Chrome
Just to confirm with everyone, is this the issue that you are running into:
More or less, I never see the Playcanvas Load screen, and i my other tabs are frozen but still remember the last frame rendered.
Thanks, do any of you have some WASM library in the project? Ammo, Basis etc?
I had the same issue.
The project was using Ammo Wasm. What helped me on that occasion is that I removed the old Ammo folder from the project assets and imported a fresh new one.
Edit:
The trick that helped me before doesnāt actually work. The app keeps freezing.
Same as this, the cause was the WASM files. And yes the crashing was exactly like your video.
Faced this again. After some digging, I noticed that the JS heap memory is not freed after refresh. A new tab just keeps asking for more.
When have people been seeing this issue? Has it been over the last week or so?
For me, itās been at the start of this week.
Around a week a for me or so.
Edit:
What helped me before (re-iporting Ammo) doesnāt actually work. Importing new Ammo Wasm doesnāt resolve the issue where GC fails to free the allocated memory for Wasm when a browser tab is closed.
Iām struggling again with trying to get a crash
Submitted bug to Chromium: 1257249 - chromium - An open-source project to help move the web forward. - Monorail
@yaustar I think you can repro this by an empty project with a single script that creates a hundred or two physical spheres in a loop on initialize. If you launch it, then keep an eye on the heap, while refreshing or reopening the tab. After some tries the app will freeze.
I tried it with a fork of this project earlier today and it just wouldnāt crash. Heap looked fine too Creating Rigid Bodies in Code | Learn PlayCanvas
Started sometime last week.