Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Foobar 2.1 64 bit crashes almost daily (Read 2014 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar 2.1 64 bit crashes almost daily

I've been sending the crash reports, but Foobar is crashing "just sitting there" (like overnight, it's crashed by morning). This is happening almost daily. I've been routinely sending crash reports but I didn't see anything in the 2.1.1 changelog that gives me hope that my issue was fixed. The only thing I can think of that's "different" is that my DAC is set as the output device and I do turn it off without quitting Foobar. Any thoughts?

Re: Foobar 2.1 64 bit crashes almost daily

Reply #1 –
If you shared a sample crashlog someone could help identify a possible cause from it. Or you could try the built-in troubleshooter, accessible from Help menu. The command is called 'Online troubleshooter'. It will send a list of your components to the crashlogger backend and show you any troublemakers.

Anyway, the changelog doesn't mention any crash fixes because there have been no bugs of that type to fix. Occasionally crashes caused by third party components can be worked around by the core, but that's rare.

To summarize: there are zero known crash bugs in the player or in any first party component.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #2 –
Crash reports seem to point at D2D / visualisations. Please try turning off hardware accelerated visualisations in advanced preferences.
Microsoft Windows: We can't script here, this is bat country.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #3 –
I have disabled hardware acceleration. We shall see if crashes occur less frequently! Attached is my most recent crash report:

Illegal operation:
Code: C0000005h, flags: 00000000h, address: 00007FFE9409169Dh
Access violation, operation: read, address: FFFFFFFFFFFFFFFFh
Last win32 error: 126

Call path:
app_mainloop=>main_thread_callback::callback_run

Code bytes (00007FFE9409169Dh):
00007FFE9409165Dh:  CC CC CC 48 83 EC 28 48 85 C9 74 10 48 8B 05 F0
00007FFE9409166Dh:  4B 16 00 48 85 C0 0F 85 9B 6B 09 00 32 C0 48 83
00007FFE9409167Dh:  C4 28 C3 CC CC CC CC CC CC CC CC 71 B9 DF 5A A1
00007FFE9409168Dh:  8F 48 C5 48 83 EC 28 65 48 8B 04 25 30 00 00 00
00007FFE9409169Dh:  F0 0F BA 71 08 00 48 8B 40 48 73 13 48 89 41 10
00007FFE940916ADh:  33 C0 C7 41 0C 01 00 00 00 48 83 C4 28 C3 CC 48
00007FFE940916BDh:  39 41 10 75 0B FF 41 0C 33 C0 48 83 C4 28 C3 CC
00007FFE940916CDh:  E8 0E 00 00 00 EB E2 CC CC CC CC CC CC CC CC CC

Registers:
RAX: 0000006D8DCF5000, RBX: 0000022EFC81B101, RCX: BF5B9D4A00000000, RDX: 0000000000000000
RSI: 0000000000000004, RDI: 00000000426D2AF0, RBP: 0000006D8DBCC209, RSP: 0000006D8DBCC100

Timestamp:
16950922ms

Crash location:
Module: ntdll
Offset: 2169Dh
Symbol: "RtlEnterCriticalSection" (+Dh)

Re: Foobar 2.1 64 bit crashes almost daily

Reply #4 –
Version 2.* crashes 90% of the time when closing the application.
One thing I found interesting is that the DB it uses (config.sqlite, metadb.sqlite) had problems so I deleted them, and the problem stopped for a week and now it crashes again although less often. I check the DB now and they have no problems.
I used to click "Send Report" but I am not sure who collects these logs so I am not sending them anymore.
I'm trying to upgrade to 64-bit to see if it will cease.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #5 –
Quote from: Gabriel Schwartz on
Version 2.* crashes 90% of the time when closing the application.
In my case, it's sitting idle, like overnight, and it's crashed by morning. It's actually never crashed for me while playing music or opening/closing the app. Foobar was rock solid for many years in the 1.x 32 bit era. I'm sure this is just growing pains with the new architecture and whatnot, so I'll ride it out but hopefully Peter can get to the bottom of this!

Re: Foobar 2.1 64 bit crashes almost daily

Reply #6 –
Quote from: Gabriel Schwartz on
Version 2.* crashes 90% of the time when closing the application.
One thing I found interesting is that the DB it uses (config.sqlite, metadb.sqlite) had problems so I deleted them, and the problem stopped for a week and now it crashes again although less often. I check the DB now and they have no problems.
I used to click "Send Report" but I am not sure who collects these logs so I am not sending them anymore.
I'm trying to upgrade to 64-bit to see if it will cease.
The crash logs are shared to component developers when relevant and of course Peter uses them to fix bugs in the core. Or for example to create workarounds for Wine bugs.
How did you determine DBs to have problems? Also database problems shouldn't cause crashing, if they do that needs fixing.

Quote from: antagron on
In my case, it's sitting idle, like overnight, and it's crashed by morning. It's actually never crashed for me while playing music or opening/closing the app. Foobar was rock solid for many years in the 1.x 32 bit era. I'm sure this is just growing pains with the new architecture and whatnot, so I'll ride it out but hopefully Peter can get to the bottom of this!
All your crashes happen in Intel drivers when dealing with DirectX acceleration. Since you turned off the hardware acceleration from built-in visualizations those drivers will never get loaded into foobar2000 process. So you should be safe from crashing from now on.

If your crash cause is the same as the one causing memory leaks for some other Intel graphics users, the upcoming v2.2 contains a fix for that. I hope it's the same problem, but I don't see how memory leak is related to the ever present win32 error 126 in your crash logs. That error means ERROR_MOD_NOT_FOUND. But perhaps that error code isn't related to the crash and it's just something irrelevant that is handled fine.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #7 –
Wild stab in the dark: maybe foo_enhanced_spectrum_analyzer uses D2D/hardware acceleration? I see that in the component list in the attached log.

Even if it doesn't, you should be trying a clean portable install with zero components and hardware acceleration for built in visualisers disabled. Then you can safely rule out 3rd party components as the cause.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #8 –
Quote from: Case on
Quote from: Gabriel Schwartz on
Version 2.* crashes 90% of the time when closing the application.
One thing I found interesting is that the DB it uses (config.sqlite, metadb.sqlite) had problems so I deleted them, and the problem stopped for a week and now it crashes again although less often. I check the DB now and they have no problems.
I used to click "Send Report" but I am not sure who collects these logs so I am not sending them anymore.
I'm trying to upgrade to 64-bit to see if it will cease.
The crash logs are shared to component developers when relevant and of course Peter uses them to fix bugs in the core. Or for example to create workarounds for Wine bugs.
How did you determine DBs to have problems? Also database problems shouldn't cause crashing, if they do that needs fixing.

Use DB Browser for SQLite and run:
PRAGMA integrity_check;

After deleting these files, the media was rebuilt, and it crashes less often.
I don't have problems at runtime as I am not using any visualizations, only at shutdown.



MOD edit: replace missing /quote (for quoted text I could find)

Re: Foobar 2.1 64 bit crashes almost daily

Reply #9 –
Yes, after a crash, deleting the config.sqlite configuration file will prevent it from crashing for a while, but at any time in the future, the crash will occur again. This issue occurs in both foobar2000 x86 2.1 and 2.1.1 versions

Re: Foobar 2.1 64 bit crashes almost daily

Reply #10 –
Care to post crash reports, @Gabriel Schwartz and @yeyo.
I recall there was some component that saves in config how many times it has been used and once certain number comes up, it starts doing some extra work. I suspect a situation like this is why config file removal prevents your crashes for a moment.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #11 –
@antagron - care to update to foobar2000 v2.1.2 and enable hardware accelerated visuals again? It includes workaround for the one found problem with some Intel drivers. Perhaps that solved your issue too.

Re: Foobar 2.1 64 bit crashes almost daily

Reply #12 –
Quote from: Case on
Care to post crash reports, @Gabriel Schwartz and @yeyo.
I recall there was some component that saves in config how many times it has been used and once certain number comes up, it starts doing some extra work. I suspect a situation like this is why config file removal prevents your crashes for a moment.

I thought crash dumps are sent when I do so in fb2k but I will attach them next time it occurs.
 

Re: Foobar 2.1 64 bit crashes almost daily

Reply #13 –
Crash dumps are sent for analyzing when you click the appropriate button. I can for example see that majority of the latest uploaded crashes are caused by SACD input and related ASIO+DSD components, then there's a share of foo_openlyrics and foo_uie_lyrics3 caused crashes. And some caused by foo_tagbox and foo_dynamic_range.

I don't have access to information to pinpoint which of the crash logs belong to you. Peter could do it but let us not bother him when not necessary.