Bug report: foobar2000 crash with foo_input_sacd 2.0.8
Status: Inactive
Brought to you by:
manisiutkin
Menu
▾
▴
1 Attachments
#217 Bug report: foobar2000 crash with foo_input_sacd 2.0.8
⚠️ Bug report: foobar2000 crash with foo_input_sacd 2.0.8
foobar2000 crashes with a Microsoft Visual C++ Runtime error.
The crash dump shows foo_input_sacd.pdb loaded at the time of the crash.
The issue occurs when using Explorer Tree Panel (foo_uie_explorer) to browse folders, even if they only contain FLAC/MP3 files.
With the previous version foo_input_sacd 1.5.11, the problem does not occur → the crash is specific to 2.0.8.
Dump result: Unknown exception, with both foo_input_sacd and foo_uie_explorer modules active.
👉 Conclusion: there is an incompatibility between foo_input_sacd 2.0.8 and Explorer Tree Panel.
Workarounds: downgrade to 1.5.11 or disable Explorer Tree Panel and use Album List / Add Folder instead.
Discussion
Anonymous
crash reports
I installed v.2.0.8 (with exact vis enabled) and my foobar (2.25.) crashed 4 times within 15 minutes. Downgraded to 2.0.7 - no crashes so far.
But I didn't ask this question, I don't even know what this is: exact visualization.
Maxim V.Anisiutkin I kindly ask you to answer my questions, however I installed foo_input_sacd-2.0.9, and the error has not appeared anymore, at least for the moment, if it appears again I will let you know always here.
Did it crash when exact visualization is disabled?
I tested with "Output → Type" set to both DSD and PCM.
The crash still occurs in both cases when using the Explorer Tree Panel and scrolling through folders.
OK, maybe the problem occurs when I check the DSD Visualization box, because when it’s not selected, the error doesn’t appear.
Nothing to do, I tried this morning with DSD Visualization checked and unchecked, and the error appears anyway.
crash reports
v.2.0.9 chrashes like 2.0.8.
V.2.0.7 works (except stuttering with foo_skip enabled).
Crash dumps for v2.0.9?
No crashes with foo_input_sacd-2.0.9
Thanks
I attached 5 crash reports from versions 2.0.8, 2.0.9 and 2,0.10. No crashes from 2.0.7 so far.
I can't reproduce this.
Maxim V. Anisiutkin, I don't understand why you reply to the guy who didn't write this post, but you never reply to me, who wrote this post.
Anyway, even with foo_input_sacd-2.0.10, I don't even have runtime error problems.
My FB crashes every few minutes if v.2.0.8, 2.0.9 or 2.0.10 is installed. I do not even have to listen to dsd. I play internet radios and it crashes. All previous versions up till 2.0.7 work ok. (There is just that glitch with skip).
So: the author of the post: Bug report: foobar2000 crash with foo_input_sacd 2.0.8, it's me: RobertoSpeed, the other one who asked you two questions under my post, I don't know who he is.
That is, he asked you these two questions:
<< I installed v.2.0.8 (with exact vis enabled) and my foobar (2.25.) crashed four times within 15 minutes. Downgraded to 2.0.7 - no crashes so far. >>
<< v.2.0.9 crashes like 2.0.8.
V.2.0.7 works (except stuttering with foo_skip enabled). >>
But anyway, now with foo_input_sacd-2.0.9 I haven't had any problems. So for me, you've solved the problem I was having, and I thank you very much.
@manisiutkin I just tried "almost" clear (meaning quite new and with only a few components) install on my second laptop (win11, newest 64bit foobar) and sacd_input2.0.10 crashed after 10 seconds of random mp3 playing. It happens all the time with version 2.0.8 to 2.0.10. Version 2.0.7 works ok (but for SKIP).
Could you attach chash dumps here, please?
Todays crash dump attached.
Thanks. From this dump it looks like foobar crashes while visualizing spectrum for data with samplerate = 0. I think the content of your C:\Users\admin\AppData\Roaming\foobar2000-v2 folder is needed as well.
It is 300MB. Without ffmpeg.exe it still would be 150MB.
That's much. Maybe, user-components-x64 and configuration subfolders then?
I have mpv amongst installed plugins. That one component is about 100MB big.
Another crash. This time with 2.0.7 installed.
Crash with SACD burned on recent version of foo_input_sacd-2.0.10
Hi,
Today I tried to play a burned SACD: foobar2000 can open it, but it can't start playback, and the application crashes (in some cases even causing a system freeze).
With version foo_input_sacd-2.0.3, the same disc played correctly.
I'm attaching the two crash report files, hoping they'll help you pinpoint the cause of the problem.
Thanks in advance for your help and for your work on the plugin!