Visitar URL original
DLC Freezing Issue · Issue #3462 · DeepLabCut/DeepLabCut · GitHub
Skip to content

DLC Freezing Issue #3462

Open

Description

@mabdelha-92

Is there an existing issue for this?

  • I have searched the existing issues

Operating System

Windows 11

DeepLabCut version

3.0.1

What engine are you using?

pytorch

DeepLabCut mode

single animal

Device type

CPU

Bug description 🐛

Hello,
We have been experiencing a problem with DeepLabCut since the most recent update. The program freezes consistently, either while analyzing a video or when trying to create a video with the predicted poses.

We have tried reinstalling DeepLabCut, but the issue continues. Before the latest update, everything was working well without these problems.

Has anyone else experienced this issue, or is there a recommended solution or workaround?

Any help would be greatly appreciated.

Mona

Steps To Reproduce

Open DeepLabCut 3.0.1.
Open an existing DeepLabCut project.
Select a video for analysis.
Start Analyze Videos.
DeepLabCut begins processing the video but eventually freezes and becomes unresponsive.

The same issue also occurs when attempting to create a video with the predicted poses after analysis.

We have reproduced the issue multiple times, and it occurs consistently. We also tried reinstalling DeepLabCut, but the freezing continued.

Relevant log output

Anything else?

No response

Code of Conduct

Activity

  1. added
    bugSomething isn't working
    GUIissues relating to GUI
    on Aug 26, 2026
  2. added theissue type on Aug 26, 2026
  3. C-Achard commented on Aug 26, 2026

    @C-Achard
    Member

    Hello @mabdelha-92,

    Thank you for the report, I'm currently investigating to see whether this is a similar failure as was fixed by #3449, or if it is something else.

    A few things that would be very useful to help us get to the bottom of this:

    • Could you share the terminal output around the time the failure occurs? Without this it is much more difficult for us to locate the exact stage at which the issue occurs.
    • Could you try doing the same in ipython using the API directly? As an example, adapt the paths and shuffle as needed:
    import deeplabcut
    
    config_path = r"C:\path\to\project\config.yaml"
    video_path = r"C:\path\to\video.mp4"
    
    deeplabcut.analyze_videos(
        config_path,
        [video_path],
        shuffle=1, # change to your own
    )
    • Is the freezing tied to the analysis stopping, or is the GUI stuck while the processing continues in the terminal?
    • Is this tied to a particular video or type of video?

    Please let me know if you have any questions; if you need a workaround in the meantime, you could try reverting to the previous version that worked for you while we fix this.

    Best,
    Cyril

  4. mabdelha-92 commented on Aug 27, 2026

    @mabdelha-92
    Author
    • Here is the terminal output around the time the failure occurs (Training for epoch 200 done, starting evaluation
      Epoch 200/200 (lr=1e-05), train loss 0.00734, valid loss 0.00916
      Model performance:
      metrics/test.rmse: 78.37
      metrics/test.rmse_pcutoff: nan
      metrics/test.mAP: 36.83
      metrics/test.mAR: 40.00
      100%|██████████████████████████████████████████████████████████████████████████████████| 43/43 [00:47<00:00, 1.10s/it]
      100%|████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 20.87it/s]
      100%|████████████████████████████████████████████████████████████████████████████████| 455/455 [13:21<00:00, 1.76s/it]
      100%|████████████████████████████████████████████████████████████████████████████████| 459/459 [14:07<00:00, 1.85s/it]
      100%|████████████████████████████████████████████████████████████████████████████████| 453/453 [15:49<00:00, 2.10s/it]
      100%|████████████████████████████████████████████████████████████████████████████████| 453/453 [17:18<00:00, 2.29s/it]
      C:\Users\mabdelha\AppData\Local\miniconda3\envs\DEEPLABCUT\lib\site-packages\deeplabcut\utils\plotting.py:76: UserWarning: Starting a Matplotlib GUI outside of the main thread will likely fail.
      fig1 = plt.figure(figsize=(8, 6))
      C:\Users\mabdelha\AppData\Local\miniconda3\envs\DEEPLABCUT\lib\site-packages\deeplabcut\utils\plotting.py:83: UserWarning: Starting a Matplotlib GUI outside of the main thread will likely fail.
      fig2 = plt.figure(figsize=(10, 3))
      C:\Users\mabdelha\AppData\Local\miniconda3\envs\DEEPLABCUT\lib\site-packages\deeplabcut\utils\plotting.py:89: UserWarning: Starting a Matplotlib GUI outside of the main thread will likely fail.
      fig3 = plt.figure(figsize=(10, 3))
      C:\Users\mabdelha\AppData\Local\miniconda3\envs\DEEPLABCUT\lib\site-packages\deeplabcut\utils\plotting.py:95: UserWarning: Starting a Matplotlib GUI outside of the main thread will likely fail.
      fig4 = plt.figure()
      C:\Users\mabdelha\AppData\Local\miniconda3\envs\DEEPLABCUT\lib\site-packages\deeplabcut\utils\plotting.py:165: UserWarning: Starting a Matplotlib GUI outside of the main thread will likely fail.
      plt.show())

    • Is the freezing tied to the analysis stopping, or is the GUI stuck while the processing continues in the terminal?
      The GUI is stuck, and at the same time the analysis process stops.

    Is this tied to a particular video or type of video?
    No, I have tried one video and multiple videos. Also tried different video types

  5. C-Achard commented on Aug 28, 2026

    @C-Achard
    Member

    Thanks for the additional logs @mabdelha-92; this is directly related to the Matplotlib GUI opening in the wrong thread.

    If you disable plotting for analysis this should not occur. The issue is now fixed in #3466, and will be merged in the next release.

    Please let me know if you encounter further problems such as this one, or if you need a workaround to unblock your work.

    Best,
    Cyril

  6. C-Achard commented on Nov 2, 2026

    @C-Achard
    Member

    @MMathisLab I would reopen for now as the fix is in #3466, it just got delayed amidst other refactors but I think can still be in 3.0.3, which solves this sooner. Let me know if you disagree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

GUIissues relating to GUIbugSomething isn't working

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions