[Bugfix] Fix CUDA/CPU mismatch in threaded training #6245
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Proposed change(s)
On Windows, running with threaded: true produced “tensors on different devices” errors. Threaded trainers create tensors in multiple threads. Implicit CPU allocations (or per-thread default device changes) led to CPU-CUDA mixing and PyTorch mode stack corruption. Making device placement explicit and consistent prevents both classes of errors.
- Create action masks, observations, and RNN memories on default_device() during inference.
- ModelUtils.list_to_tensor() and list_to_tensor_list() now allocate on default_device().
- VectorInput.update_normalization() now uses device-correct tensors.
- Initialize zero RNN memories on default_device().
- Ensure DONE tensors, epsilons, and accumulators allocate on the correct device.
Useful links (Github issues, JIRA tickets, ML-Agents forum threads etc.)
Types of change(s)