-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Is there an existing issue for this?
- I have searched the existing issues
Bug description
When in the [track refinement GUI] you attempt to fast-forward the speed you are met with DeepLabCut crashing and the following error in the terminal:
QCoreApplication::exec: The event loop is already running
QObject::startTimer: Timers can only be used with threads started with QThread
.....
QObject::startTimer: Timers can only be used with threads started with QThread
Assertion fctx->async_lock failed at libavcodec/pthread_frame.c:173
I mentioned this to Konrad Danielewski, who I beleive commented on it in a different pull-request: Here
Operating System
Windows 11
DeepLabCut version
v2.3.0
DeepLabCut mode
multi animal
Device type
RTX4080
i5-12600K
Steps To Reproduce
- Open DLC's [Track Refinment GUI]
- Attempt to speed-up the frames/tick by using [Alt]-[Forward]
- Crash
Relevant log output
QCoreApplication::exec: The event loop is already running
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
Assertion fctx->async_lock failed at libavcodec/pthread_frame.c:173Anything else?
The lack of this features makes the fixing of occasional identity swaps in a highly interacting species over hours of video very difficult if not impossible given the sluggishness of the GUI in general.
Thank you for any help in this matter
Code of Conduct
- I agree to follow this project's Code of Conduct