Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-68436

webassembly: runtime not being exited

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: P3: Somewhat important P3: Somewhat important
    • None
    • 5.11.0 RC 1
    • QPA
    • None
    • WebAssembly
    • e5b00102a40c15f0d6c72c3e9d53c1e08d6cc9b9

      emscripten recently changed NO_EXIT_RUNTIME default to 1, meaning the runtime is not exited.

      https://kripken.github.io/emscripten-site/docs/getting_started/FAQ.html#what-does-exiting-the-runtime-mean-why-don-t-atexit-s-run

      "Which means that we don't include code to shut down the runtime. That means that when main() exits, we don't flush the stdio streams, or call the destructors of global C++ objects, or call atexit callbacks."

      If you are running several Qt Webassembly runetimes (such as with testing), the browser will eventually run out of memory.

      We need to add -s NO_EXIT_RUNTIME=0 to link line.

        For Gerrit Dashboard: QTBUG-68436
        # Subject Branch Project Status CR V

            lpotter Lorn Potter
            lpotter Lorn Potter
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes