Megvii-BaseDetection / Megvii-BaseDetection/YOLOX
yolox_s stuck at epoch3 when training custom data
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.6k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached train_log.txt and the reported Windows 11 WSL2 environment, focusing on what changes at epoch 3 and how GPU memory behaves. Trace the custom-data training entry point and reproduce the hang; done means training proceeds beyond epoch 3 without the reported stall or unreleased GPU memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100