-
Notifications
You must be signed in to change notification settings - Fork 726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should TensorboardWriter
close its tf.summary.FileWriter
?
#855
Comments
Maybe the context That way we don't create a new FileWriter, therefore a new events file every time we call I'm ending up with long and growing list of files like:
Granted, I can just rely on the ep reward mean logs from |
Hello, Maybe a duplicate of #501 |
new_tb_log==False here does not work? |
There is an issue about that: #599 (comment) |
PPO2 uses a
with TensorboardWriter(...) as writer:
context thatflush
es but doesn't ever close itstf.summary.FileWriter
. This led to (in combination with another problem on my side) a "too many files are opened by this process" error in one of my runs when I calledPPO2.learn()
repeatedly.Maybe the intention here is to allow us to access the same
FileWriter
later, but a second call toPPO2.learn()
in facts opens a new events file and creates a newFileWriter
, which again is not closed by the time thatlearn
exits.Relevant lines in
TensorboardWriter
:stable-baselines/stable_baselines/common/base_class.py
Lines 1137 to 1145 in 6347da3
stable-baselines/stable_baselines/common/base_class.py
Lines 1161 to 1164 in 6347da3
The text was updated successfully, but these errors were encountered: