Skip to content
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

Shaping in health_gathering sometimes crashes #74

Closed
schrum2 opened this issue Jun 1, 2016 · 3 comments
Closed

Shaping in health_gathering sometimes crashes #74

schrum2 opened this issue Jun 1, 2016 · 3 comments

Comments

@schrum2
Copy link

schrum2 commented Jun 1, 2016

This error is annoying because it only happens periodically. I'm using the Shaping.java file in conjunction with the downloaded version 1.0.3 binary for Windows. I only noticed this error after doing this, but because it happens periodically, it may have been an issue before. The CFG and WAD are for the health_gathering task. I receive:

Exception in thread "main" vizdoom.ViZDoomUnexpectedExitException: Controlled ViZDoom instance exited unexpectedly.
at vizdoom.DoomGame.makeAction(Native Method)
at vizdoom.examples.Shaping.main(Shaping.java:72)

The specific line causing the problems is
double r = game.makeAction(actions.get(ran.nextInt(3)));
Even if I change the code to the following,
double r = game.makeAction(actions.get(0));
I sometimes get the error. The code crashes roughly 1 in 5 times, but there is a lot of variation.

Interestingly, when the code crashes, it is ALWAYS on the first action. The error is not occurring at some point in the middle of evaluation, but always at the very start of the very first episode.

@mwydmuch mwydmuch added the bug label Jun 1, 2016
@mwydmuch
Copy link
Member

mwydmuch commented Jun 1, 2016

I confirm that it happens on windows on 1.0.2 and 1.0.3. 1.0.1 works well so You can use this version for now. I will investigate this.

@mwydmuch
Copy link
Member

Sorry, I forgot a bit about this issue, however I think it has just been solved in new 1.1.0pre and 1.0.4 build.

@mwydmuch
Copy link
Member

mwydmuch commented Dec 6, 2016

I've checked again and I cannot reproduce this bug anymore (tested on Linux and Windows), so I'm closing this issue.

@mwydmuch mwydmuch closed this as completed Dec 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants