Jump to content


BUG 10.3.2 - Accordance Hangs Upon Close if Not Interacted With for Some Number of Hours

  • Please log in to reply
No replies to this topic

#1 Matt Fredenburg

Matt Fredenburg


  • Active Members
  • PipPipPipPip
  • 326 posts
  • Gender:Male
  • Accordance Version:12.x
  • Platforms:Windows, iOS

Posted 13 November 2013 - 01:29 PM

I'm reporting this because I've seen this at least three times now. To duplicate (for me):


  1. Start Accordance
  2. Open a workspace
  3. Do stuff in Accordance
  4. Leave the computer on and Accordance running (but not interacted with) for at least 20 hours or so
  5. Exit Accordance via File->Quit
  6. The workspace closes (i.e. Accordance still shows a UI, but a blank 'workspace')
  7. Accordance hangs with 0 CPU and I/O
  8. Windows reports that Accordance has stopped responding and Accordance must be forcibly closed

Upon opening Accordance again, Accordance does *not* report that it had been forcibly closed, and simply opens the workspace in the state that it was prior to step 5 above.




  • Windows 10 Pro 10.0.14393
  • Accordance 12.0.2
  • i7-6800K @ 3.40 GHz
  • 64 GB RAM
  • Nvidia 1080 GTX 8GB VRAM

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users