Bug #8541

[NodeManager] Use sys.exc_clear() to release exception tracebacks

Added by Peter Amstutz over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

According to the discussion at http://cosmicpercolator.com/2016/01/13/exception-leaks-in-python-2-and-3/ exceptions can keep stack frames live far past when they are no longer needed, which may be the cause of our memory leaks.

Audit exception handling in node manager and use sys.exc_clear() discard exception tracebacks where possible.


Related issues

Related to Arvados - Story #8543: [NodeManager] Don't use Futures when not expecting a replyResolved03/04/2016

History

#1 Updated by Peter Amstutz over 4 years ago

  • Description updated (diff)

#2 Updated by Brett Smith over 4 years ago

  • Target version set to Arvados Future Sprints

#3 Updated by Peter Amstutz over 4 years ago

#8543 is another line of inquiry related to exceptions possibly sticking around for much longer than they should.

#4 Updated by Brett Smith over 4 years ago

Our current thinking is that #8543 has improved the situation enough (based on RSS) that this should no longer be necessary, right?

#5 Updated by Peter Amstutz over 4 years ago

Yes. While it's still possible it's holding onto some exceptions unnecessarily, it looks like #8543 solved the primary memory leak, so this ticket is low priority.

Also available in: Atom PDF