Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-318

Threads seem to freeze under OS X when changing network

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0522
    • Component/s: Threading
    • Sprint:
      Sprint Drive 7.2-4

      Description

      To reproduce: close the Mac and reopen it with another network.

      When quitting we get:

      2015-04-29 10:28:00,971 6215 140735098516224 DEBUG    nxdrive.wui.dialog Load web file : /Applications/Nuxeo Drive.app/appdata/Nuxeo Drive-2.0.0427.macosx-10_7-x86_64/Nuxeo Drive.app/Contents/Resources/ui5/systray.html
      2015-04-29 10:28:01,171 6215 140735098516224 TRACE    nxdrive.wui.application Received Qt application event
      2015-04-29 10:28:03,509 6215 140735098516224 DEBUG    nxdrive.manager    Stop engine 8ceff77dbc5311e4836e20c9d089f363
      2015-04-29 10:28:03,509 6215 140735098516224 DEBUG    nxdrive.engine.engine Engine 8ceff77dbc5311e4836e20c9d089f363 stopping
      2015-04-29 10:28:03,779 6215 4546326528 DEBUG    nxdrive.engine.workers Thread RemoteWatcher(4546326528) interrupted
      2015-04-29 10:28:04,075 6215 4490997760 INFO     nxdrive.engine.watcher.local_watcher Stopping FS Observer thread
      2015-04-29 10:28:04,268 6215 4490997760 DEBUG    nxdrive.engine.workers Thread LocalWatcher(4490997760) interrupted
      2015-04-29 10:28:09,283 6215 140735098516224 WARNING  nxdrive.engine.engine Thread is not responding - terminate it
      2015-04-29 10:28:14,284 6215 140735098516224 WARNING  nxdrive.engine.engine Thread is not responding - terminate it
      2015-04-29 10:28:19,285 6215 140735098516224 WARNING  nxdrive.engine.engine Thread is not responding - terminate it
      2015-04-29 10:28:34,288 6215 140735098516224 DEBUG    nxdrive.engine.engine Engine 8ceff77dbc5311e4836e20c9d089f363 stopped
      2015-04-29 10:28:34,316 6215 140735098516224 DEBUG    nxdrive.commandline Qt application exited with code 0
      

      When such a freeze occurs we should have a timeout.
      Maybe we could ping the threads regularly to se if they're not blocked, if they are kill and restart them (might need a fullscan).

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: