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

QWebEngineViews: MojoDiscardableSharedMemoryManagerImpls leaking, processes can't be terminated, worker threads

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2: Important
    • Resolution: Duplicate
    • Affects Version/s: 5.11.1
    • Fix Version/s: None
    • Component/s: WebEngine
    • Labels:
      None
    • Environment:
      Win 10 Enterprise
      Qt Creator 4.7.0
    • Platform/s:
      Windows

      Description

      I actually have seen this in Windows 10, in Qt Creator, in Debug

      In other cases I've seen the qtwebengine worker threads still running after the application has quit.

      It seems to depend on how you "quit" .. in one case I used File > Quit which invoked QApplication::quit()

      It produced this output:

      [12820:5672:0807/114650.847:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.847:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.886:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.886:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.913:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.913:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.913:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:5672:0807/114650.913:ERROR:process_win.cc(151)] Unable to terminate process: Access is denied. (0x5)
      [12820:11540:0807/114650.932:WARNING:discardable_shared_memory_manager.cc(436)] Some MojoDiscardableSharedMemoryManagerImpls are still alive. They will be leaked.
      [12820:11540:0807/114650.932:WARNING:discardable_shared_memory_manager.cc(436)] Some MojoDiscardableSharedMemoryManagerImpls are still alive. They will be leaked.
      11:46:51: /debug/app exited with code 0

      In another case, during my closeEvent, I invoke the following event->accept() without QApplication:quit()  .. the result was that even though the application window had closed, the worker threads were still alive and reporting keep-alives back through the websocket.  This apparently was because even though I did an event->accept() on the close event of the main window, I did not invoke QApplication:quit() .. so I'll investigate that myself. 

       

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              qt_webengine_team Qt WebEngine Team
              Reporter:
              h3rb Herb Gilliland
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes