-
Notifications
You must be signed in to change notification settings - Fork 108
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
Error "cannot join thread before it is started" after upgrading to 3.0.0 #115
Comments
Thanks, I will check the implementation, because I'm not using it directly but via some other package, not sure which one. Let me dig into. |
I don't think it's related to the latest changes. In the traceback in the screenshot line 300 in ffdec.py is @loretoparisi maybe you can provide a |
Indeed—maybe it would also be worth trying the same code on an older version to check whether the crash is truly new? |
Thanks for helping guys, it seems we use it from librosa, and I assume it is using the pypi version so it should be in fact not the latest one from what I can see. Since the error I see here is a threading error (join), what I'm not sure of, is if originates internally in your sdk due to I/O access issues, and throws outsides, or the log just says that while the FFPMEGAudioReader thread was running something externally occurred... |
Did you get anywhere with resolving this @loretoparisi? I'm encountering the same issue using librosa to load audio from mp4 files. |
nope I moved to native ffmpeg. |
@DWhettam can you please share a stacktrace of the error that you see? |
Sure. I get the "cannot join thread before it is started error" as well as "can't start new thread". I also get "Format not recognised." on the mp4 videos. This error occurs on a different mp4 each time, and only occurs for me when I try to read the audio and video from the mp4 file, if I just load the audio, or the video, I don't have any issues, so I'm fairly certain there is no issue with the files themselves, as I do not get that issue when reading the audio files. More specifically, if I call read_video(uses pytorchvideo), I have no errors. If I call read_audio(using librosa), I have no issues. But if I call one after the other, I encounter the below issue. Any help would be greatly appreciated!
|
@Bomme by reducing the number of workers in my pytorch dataloader I am able to run the code for much longer, although the error is still occurring. Instead of within the first epoch of training, reducing the number of workers causes the error to occur in the sixth epoch. I'm not sure what to interpret from this, but at least this confirms the "Format not recognised" part of the stack trace is a misnomer. |
Hello, I'm getting this threading error, after upgrading to the latest version.
This is currently my full stack trace
The text was updated successfully, but these errors were encountered: