RVC-Project / RVC-Project/Retrieval-based-Voice-Conversion-WebUI

Process 0 terminated with the following error:

Open
#130 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted
Dominant language
Python
Stars
38.4k
Forks
5.3k
PR merge metrics
No merged PRs in 30d

Description

I use RTX3060ti.

-- Process 0 terminated with the following error:
Traceback (most recent call last):
File "C:\RVC-beta\RVC-beta\runtime\lib\site-packages\torch\serialization.py", line 441, in save
_save(obj, opened_zipfile, pickle_module, pickle_protocol)
File "C:\RVC-beta\RVC-beta\runtime\lib\site-packages\torch\serialization.py", line 668, in _save
zip_file.write_record(name, storage.data_ptr(), num_bytes)
RuntimeError: [enforce fail at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\caffe2\serialize\inline_container.cc:476] . PytorchStreamWriter failed writing file data/2229: file write failed

RuntimeError: [enforce fail at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\caffe2\serialize\inline_container.cc:337] . unexpected pos 256653056 vs 256652948

I tried several times but all cases made like this error.(like 256653056 vs 256652948,this number is changed by in cace.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the traceback in runtime/lib/site-packages/torch/serialization.py and the reported Windows RTX3060ti environment, then reproduce the failing save operation. Compare the changing file-write positions in the error output. Done means identifying a verified project-level cause and documenting or implementing a confirmed resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.