-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using wasm drop
method results in warnings flood
#6505
Comments
This is more serious than it looks. If we are still trying to render after the drop, when Pawel will create a new project after the drop and re-initialize the app, we can have WebGL errors in the new instance because of that. |
Adam Obuchowicz reports a new STANDUP for yesterday (2023-06-13): Progress: A little progress yesterday, as I spent most time on reviewing Wojciech's PR. Tried to find which Callback is left in JS. Found that only keydown events are printing the error log. It should be finished by 2023-06-14. Next Day: Next day I will be working on the #6850 task. If time allows (I still need to finish review), I will start implementing the designed solution for "not-connectable" ports problem. |
1. Fixed leaks of Scene. We were making several cycles of Rc references. 2. Fix removing event listeners: the remove listener option should take same options as those passed in addEventListener. This should finally fix #6505
@farmaazon, unfortunately, @PabloBuchu can still observe the regression here |
@xvcgreg what do you mean? Do you have any additional info? |
@farmaazon just a direct message from @PabloBuchu that he can observe the problem still - please contact him directly as he has observed the issue. |
@PabloBuchu should post here the details probably. |
@farmaazon sorry was to fast to reopen.. I can't know reproduce it.. Normal drop works fine as intendent, but couple of times I got framebuffer warnings again. Closing for now |
@farmaazon is this related to this bug or is it because my project failed for some other problems? When I closed the project I got a lot and
Screen.Recording.2023-07-04.at.09.56.24.mov |
I don't know where "console.assert" messages come from, but the warnings suggest there is still some rendering done, so probably it's somehow relevant. |
Closing as wont be fixed given VueJS move. |
This is an issue to fix leftovers after implementing
wasm.drop
method. Original problem was rised during QAing #6365 (comment)Steps to reproduce:
-debug.dev-tools
flagensoglApp.wasm.drop()
https://drive.google.com/file/d/1Oy3-D5JGYy4PbJhYAXYXB3Ouuks_zL45/view?usp=share_link
The text was updated successfully, but these errors were encountered: