open-mmlab / mmdetection3d

OpenMMLab's next-generation platform for general 3D object detection.
https://mmdetection3d.readthedocs.io/en/latest/
Apache License 2.0
5.35k stars 1.55k forks source link

[Bug] LOG_PROCESSORS get stucked when debugging with VSC #3033

Open rumjie opened 2 months ago

rumjie commented 2 months ago

Prerequisite

Task

I have modified the scripts/configs, or I'm working on my own tasks/models/datasets.

Branch

1.x branch https://github.com/open-mmlab/mmdetection3d/tree/dev-1.x

Environment

sys.platform: linux Python: 3.7.10 (default, Feb 26 2021, 18:47:35) [GCC 7.3.0] CUDA available: True numpy_random_seed: 2147483648 GPU 0,1,2,3: NVIDIA GeForce RTX 3090 CUDA_HOME: /usr/local/cuda NVCC: Cuda compilation tools, release 11.1, V11.1.105 GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 PyTorch: 1.9.0 PyTorch compiling details: PyTorch built with:

TorchVision: 0.10.0 OpenCV: 4.8.1 MMEngine: 0.9.1 MMDetection: 3.2.0 MMDetection3D: 1.4.0+3aa4ed4 spconv2.0: False

Reproduces the problem - code sample

cd mmdetection3d/tools ; /usr/bin/env /opt/conda/bin/python /root/.vscode-server/extensions/ms-python.debugpy-2024.0.1-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher 49601 -- mmdetection3d/tools/train_debug.py mmdetection3d/configs/parta2/parta2_base.py

Reproduces the problem - command or script

tools/train.py

Reproduces the problem - error message

no error message, just VSC debugger is stucked

Additional information

There is custom config file and kitti dataset, and training process goes without any errors. However, when I run the same code on VSC debugger, code always stucked (or pending?) on the line below.

image