Unity-Technologies/obstacle-tower-env

Environment hangs up when spawning from different processes

Open

#75 opened on Mar 18, 2019

View on GitHub
 (16 comments) (0 reactions) (2 assignees)Python (127 forks)batch import
help wanted

Repository metrics

Stars
 (538 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hello,

I'm trying to run the obstacle tower environment through the large-scale-curiosity project. However, it seems to hangup when it tries to create the environment from its subprocesses. It prints out that the CrashReporter is initalized and the mono config paths, then does nothing for a while and hangs up with the following image:

image

This is run on a MBP 13'' 2018, without a GPU. Any way to troubleshoot and debug this? I can't really do anything as there aren't really logged anything from inside the environment.

Contributor guide

Research direction
Investigate the hang during environment initialization from subprocesses. Focus on the Unity player startup sequence, especially the CrashReporter and mono config paths. Check if the issue is specific to macOS without GPU. Review the Unity player logs and consider running the environment with verbose logging enabled. Look at the obstacle tower env Python wrapper's process spawning code and any related issues or PRs.
Tech stack
python
Domain
machine learning
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Python environment setupUnity ML Agents
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20