writer is never closed
See original GitHub issueHi,
https://github.com/lanpa/tensorboard-pytorch/blob/master/tensorboardX/record_writer.py
self._writer = open(path, 'wb')
is never closed
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Resource leak: 'in' is never closed - java - Stack Overflow
@Borat - "resource leak" implies that some system resource (usually memory) is being lost or wasted needlessly. Usually this will impact you ...
Read more >Help with Warning: Resource leak: 'input' is never closed
I keep getting the warning that : Resource leak: 'input' is never closed I have never got ... Is there a right and...
Read more >Resource leaks in Java: FileWriter not closing issue
By putting it all in a try-catch block, the catch list (shown below) would cause the warning message “Resource leak: 'FileWriter' is not...
Read more >What is this error in Java, “resource leak: 'keyboard' is never ...
The IDE is trying to warm you that the the scanner object that was created, if kept without closing, will lead to resource...
Read more >561589 – Unexpected "Resource leak is never closed" warnings
Bug 561589 - Unexpected "Resource leak is never closed" warnings ... (unrelated to the reader and writer), eg. the last for loop, the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@lanpa IMHO this should be fixed asap. This is a very serious issue. Opening 10 SummaryWriter creates close to 3k open files. Even after updating to tensorboardX==1.2.
the .close() method has no effect.
Any updates on this?