RVC-Project / RVC-Project/Retrieval-based-Voice-Conversion-WebUI
warnings.warn('resource_tracker: There appear to be %d '
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38.4k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
Hello dear all. I had an error.
System: Ubuntu 24.04
GPU: 2x3090
Ram: 128Gb
Python version 3.9.8
Can you please help me, where I'm wrong?
Traceback (most recent call last):
File "/usr/local/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/local/lib/python3.9/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/home/saif/saif/Retrieval-based-Voice-Conversion-WebUI/infer/modules/train/train.py", line 282, in run
train_and_evaluate(
File "/home/saif/saif/Retrieval-based-Voice-Conversion-WebUI/infer/modules/train/train.py", line 496, in train_and_evaluate
scaler.scale(loss_gen_all).backward()
File "/home/saif/saif/venv/env398rvc/lib/python3.9/site-packages/torch/_tensor.py", line 487, in backward
torch.autograd.backward(
File "/home/saif/saif/venv/env398rvc/lib/python3.9/site-packages/torch/autograd/init.py", line 200, in backward
Variable._execution_engine.run_backward( # Calls into the C++ engine to run the backward pass
RuntimeError: [../third_party/gloo/gloo/transport/tcp/pair.cc:589] Read error [127.0.1.1]:20909: Connection reset by peer
/usr/local/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 20 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '
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 infer/modules/train/train.py at lines 282 and 496, then trace the multiprocessing and Gloo setup associated with the reported backward failure. Reproduce the training run with the stated Python and Ubuntu details, determine why the peer connection resets, and verify that training completes without the semaphore-leak warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- distributed-systems, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100