-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
LMMS crashes if i'm using a wav-file in the sampletrack #4328
Comments
Do you have a backtrace for the crash? |
gdb telling me this: `terminate called after throwing an instance of 'std::bad_alloc' Thread 12 "QThread" received signal SIGABRT, Aborted. "Datei oder Verzeichnis nicht gefunden." = "File or directory not found." |
Could you type |
|
in another projects i get this output:
|
Thanks for the backtrack.FYI, you can wrap the backtrace with ```. |
I can reproduce this with all kind of waves. I can reproduce on two different ubuntus (17.10 and 16.04 both 64bit) This is the master branch.
|
Could you please upload a file that causes this crash? Since I've made a few large changes to SampleBuffer on #3947 , I want to check if it has solved that already. Ok. so i've tried to crash it with https://commons.wikimedia.org/wiki/File:245286_dbspin_grunewald.wav without success on the recording pr. could you try to reproduce it with this file? |
had the same bug |
On master: every sample I've tested in the sampletrack crashes lmms. #3947 seems to fix that for me. |
Then I guess it's #4310 (comment). |
Can we cherry-pick relevant commits from #3947 and close this? |
@PhysSong You could just apply Reflexe@18a7f28 |
yes, it works...thx Reflexe :) |
if i'm putting a bigger sample (2-3 mins) in the sample track, i can playback the project 1 times.
the second time LMMS crashes immediately with following message:
terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc [1] 12580 abort (core dumped) lmms
the same wav-file in the AudioFileProcessor works fine.
LMMS 1.2.0-RC5.293 / Linux 64bit, QT 5.9.5
The text was updated successfully, but these errors were encountered: