That looks like a regression. Could you open a bug for this? Also, can you confirm that https://github.com/emscripten-core/emscripten/commit/c41f6590b1f9fcda12b2adb2d32cd352f163e717 is the culprit? i.e. reverting this fixes the issue for you?
cheers, sam On Thu, Aug 22, 2024 at 6:44 AM Stephan Bergmann <sberg....@gmail.com> wrote: > After upgrading emsdk to something that includes > < > https://github.com/emscripten-core/emscripten/commit/c41f6590b1f9fcda12b2adb2d32cd352f163e717> > > "Remove use of legacy proxy API from library_html5.js. NFC (#20370)" > (which switched code from calling `queueEventHandlerOnThread_iiii` -> > `_emscripten_dispatch_to_thread_` to calling > `_emscripten_run_callback_on_thread` -> `emscripten_proxy_sync`), I now > started to get deadlocks, in a somewhat complex scenario running a > Qt5-based LibreOffice with -sPROXY_TO_PTHREAD. > > I can get rid of those deadlocks if I change > `_emscripten_run_callback_on_thread` (in `system/lib/html5/callback.c`) > from calling `emscripten_proxy_sync` to `emscripten_proxy_async`, and I > wonder if the use of the `sync` variant was intentional in the above > commit? > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va28Sjb7TMGUYsgutHeijSPvDh47%3DKy0QWCtgucN1O%2BoKdg%40mail.gmail.com.
