-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
"Unexpected ViZDoom instance crash" during multi-threading training #169
Comments
How often does it happen? Cause I cannot replicate it. |
It always happens when I trained long enough. How can we tell there is memory leak from the information I post? |
I see that you use your own wad file. Have you checked other scenarios/wads? |
Okay, will check more wad files... I checked cig.wad, which also crashed. My own wad file "ttt2.wad" is just renamed from "multi_duel.wad" with both players changed to "deathmatch player" by slade... |
What about some singleplayer wads? Based on location of the crash, I suspect that bots may be the cause. As ZDoom wiki says (https://zdoom.org/wiki/Bots) bots are officially unsupported in current versions of engine and unfortunately aren't working perfectly with all ViZDoom features (recording functionality). On the other hand, I believe that bots were used frequently during last year competition and no one reported similar problem. I'll examine this for sure, but I'm a little busy lately, so it may take a week. |
Similar issues occurred
I used |
Hello @GoingMyWay, |
@mwydmuch The following are the details of the outputs
Since There are 4 agents training simultaneously, the maximum number of episode is 120000, however it stoped at 4250. Show
|
Has it happened again? Cause I can't replicate this (using exactly the same settings as yours) so I'm missing some significant factor in my environment or this is really really rare. |
@mwydmuch , Yes, almost every time, Would you mind me sending my code to you? |
This will be very helpful, please send it to [email protected] |
@mwydmuch , I sent code to you, thank you! |
I faced the same problem when using multi-threading. |
Hi,
I ran a A3C style training and ViZDoom crashed occasionally (The same lua/Torch code ran well with ALE environment across a wide range of games). The more threads I started, the faster it crashed... The error information is like:
and the vizdoom-crash.log is like:
The text was updated successfully, but these errors were encountered: