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
in an attempt to turn my single-threaded web application running in a browser into a multi-threaded one, I am stuck because of an issue which is hard to debug: When interacting with the canvas, events are passed to a rendering thread using a queue. This all works fine up to a situation in which the main event loop freezes (about a minute of clicking/dragging). I have added a couple of debug print statements and have noticed that this happens at different locations in the code, not at always the same one, and not at a particular one.
Interacting with web assembly via direct function calls (and not via interactions/main event loop) crashes as well, probably due to corrupt memory. The problem even occurs when limiting the number of threads to e.g. 4.
There are no messages printed, and turning on PTHREADS_DEBUG also does not reveal something interesting. Overall Memory usage was about 120 MB, which should be doable in a browser.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
in an attempt to turn my single-threaded web application running in a browser into a multi-threaded one, I am stuck because of an issue which is hard to debug: When interacting with the canvas, events are passed to a rendering thread using a queue. This all works fine up to a situation in which the main event loop freezes (about a minute of clicking/dragging). I have added a couple of debug print statements and have noticed that this happens at different locations in the code, not at always the same one, and not at a particular one.
Interacting with web assembly via direct function calls (and not via interactions/main event loop) crashes as well, probably due to corrupt memory. The problem even occurs when limiting the number of threads to e.g. 4.
There are no messages printed, and turning on PTHREADS_DEBUG also does not reveal something interesting. Overall Memory usage was about 120 MB, which should be doable in a browser.
Any advice how to continue debugging?
Thanks and best regards,
Sophonet
Beta Was this translation helpful? Give feedback.
All reactions