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

ai2thor.exceptions.UnityCrashException: Unity process has exited - check Player.log for errors #35

Closed
twb1235 opened this issue Mar 21, 2022 · 0 comments

Comments

@twb1235
Copy link

twb1235 commented Mar 21, 2022

Hi @twb1235,

Sorry, I seem to have missed this issue as it was posted during the Christmas holidays. The THOR instances should definitely be on the GPU. Is it possible that you haven't started an x-server on your GPU? Doing so is required to be able to run AI2-THOR on the GPU. Assuming you're using a recent version of ai2thor and you have X11 installed (sudo apt install xserver-xorg-core), you can do so by running:

sudo ai2thor-xorg start

This might complain that it can't find the ai2thor-xorg command in which case you can run

which ai2thor-xorg

which should print something like /your/path/to/ai2thor-xorg, you should then copy this path and run

sudo /your/path/to/ai2thor-xorg start

Hello, thank you for your reply. After opening X server,all Thor instances are running on GPU.

Recently, when I was doing one-phase training experiment, I still encountered unitycrashexception, I only started two training processes on one GPU. I found that UnityCrashException errors always occur in the Reset action
捕获4

The following figure is my training log, with only two vectorsampledtasks.
捕获6

At present, only Thor instances are running on the GPU, but it always ends after tens of thousands of steps. Can I put the vectorsampledtask: 0, vectorsampledtask: 1 sampling process on the GPU?

The following figure shows the machine parameters in the configuration file
机器参数

Originally posted by @twb1235 in #29 (comment)

@twb1235 twb1235 closed this as completed Jul 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant