Ошибка многопроцессорной блокировки при запуске программы vizdoom и pytorch в подсистеме Windows для Linux - PullRequest
0 голосов
/ 26 мая 2018

всякий раз, когда я пытаюсь запустить свою программу на WSL, я получаю следующую ошибку.Я довольно новичок в pytorch и vizdoom, поэтому я не знаю, как решить эту проблему.

Настройка
- Windows 10 x64
- Ubuntu 14 (включенWSL)
- Python 2.7.14 (Anaconda 2)
- OpenAI Gym 0.9.5
- Vizdoom 1.1.4
- doom-py 0.0.14
- ppaquette / gym-doom
- pytorch 0.0.12

(doomenv) hybridsyntax@Blacklynx:/mnt/f/_TUTORIALS/ai/doom/code$ python ai.py  > wsl.log
[2018-05-25 18:21:44,354] Making new env: ppaquette/DoomCorridor-v0
[2018-05-25 18:21:44,365] Clearing 2 monitor files from previous run (because force=True was provided)
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
Traceback (most recent call last):
  File "ai.py", line 155, in <module>
    memory.run_steps(200)
  File "/mnt/f/_TUTORIALS/ai/doom/code/experience_replay.py", line 70, in run_steps
    entry = next(self.n_steps_iter) # 10 consecutive steps
  File "/mnt/f/_TUTORIALS/ai/doom/code/experience_replay.py", line 21, in __iter__
    state = self.env.reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 104, in reset
    return self._reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/wrappers/monitoring.py", line 39, in _reset
    observation = self.env.reset(**kwargs)
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 104, in reset
    return self._reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 311, in _reset
    observation = self.env.reset(**kwargs)
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 104, in reset
    return self._reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/wrappers/frame_skipping.py", line 33, in _reset
    return self.env.reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 104, in reset
    return self._reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 283, in _reset
    return self.env.reset(**kwargs)
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 104, in reset
    return self._reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/wrappers/time_limit.py", line 49, in _reset
    return self.env.reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym/gym/core.py", line 104, in reset
    return self._reset()
  File "/mnt/f/_TUTORIALS/ai/doom/gym-doom/ppaquette_gym_doom/doom_env.py", line 244, in _reset
    return self._load_level()
  File "/mnt/f/_TUTORIALS/ai/doom/gym-doom/ppaquette_gym_doom/doom_env.py", line 157, in _load_level
    'singleton lock in memory.')
gym.error.Error: [ViZDoomUnexpectedExitException, ViZDoomErrorException] VizDoom exited unexpectedly. This is likely caused by a missing multiprocessing lock. To run VizDoom across multiple processes, you need to pass a lock when you configure the env [e.g. env.configure(lock=my_multiprocessing_lock)], or create and close an env before starting your processes [e.g. env = gym.make("DoomBasic-v0"); env.close()] to cache a singleton lock in memory.
[2018-05-25 18:21:44,696] Finished writing results. You can upload them to the scoreboard via gym.upload('/mnt/f/_TUTORIALS/ai/doom/code/videos')
(doomenv) hybridsyntax@Blacklynx:/mnt/f/_TUTORIALS/ai/doom/code$

Заранее спасибо

1 Ответ

0 голосов
/ 26 мая 2018

Обновление Ubuntu на WSL до последней версии (18.04) решило проблему для меня.

Для меня это было выполнение следующих команд на WSL.

sudo -S env RELEASE_UPGRADER_NO_SCREEN=1 do-release-upgrade
sudo apt-get update
sudo apt-get upgrade -y
...