Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processing issue - Leaked semaphore objects - There appear to be %d #349

Open
e-basaran opened this issue Aug 12, 2024 · 1 comment
Open

Comments

@e-basaran
Copy link

[DLC.CORE] Creating temp resources...
[DLC.CORE] Extracting frames...
[DLC.FACE-SWAPPER] Progressing...
Processing:   0%| | 2/1306 [00:01<16:09,  1.34frame/s, execution_providers=['CoreMLExecutionProvider'], execution_threads=8, max_memory=4Applied providers: ['CoreMLExecutionProvider', 'CPUExecutionProvider'], with options: {'CPUExecutionProvider': {}, 'CoreMLExecutionProvider': {}}
inswapper-shape: [1, 3, 128, 128]
Processing:  27%|██▋       | 359/1306 [02:04<05:59,  2.63frame/s, execution_providers=['CoreMLExecutionProvider'], execution_threads=8, max_memory=4]zsh: killed     python3 run.py --execution-provider coreml

/opt/miniconda3/lib/python3.10/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '

When I try to process a video, it gives the above error near 25%. I couldn't find a valid fix.

Regards.

@atiorh
Copy link
Collaborator

atiorh commented Aug 29, 2024

Looks like this is in the context of a broader app and the log message isn't relevant but the leaked semaphore message is usually related to running out of memory on your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants