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 crashes repeatedly (while initialising library from NAS) (Read 1418 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar crashes repeatedly (while initialising library from NAS)

Foobar (latest version) on Win10 64bit crashes repeatedly while initialising the library. The music is on a Synology with the latest software and is shared over SMB. Anyone else seeing this? Cheers.

Re: Foobar crashes repeatedly (while initialising library from NAS)

Reply #1
I gave up on SMB and assigned a drive letter to my Synology box; that works for me with no problems. Also using Win10 (Home) 64-bit.

Re: Foobar crashes repeatedly (while initialising library from NAS)

Reply #2
I gave up on SMB and assigned a drive letter to my Synology box; that works for me with no problems. Also using Win10 (Home) 64-bit.
Thanks for your reply. I already have a drive letter assigned.

Re: Foobar crashes repeatedly (while initialising library from NAS)

Reply #3
Have you sent the crash reports it generates? If you don't get a crash submission dialog post a list of your components and check application events in Event Viewer to see if the crash reason is logged there.

Re: Foobar crashes repeatedly (while initialising library from NAS)

Reply #4
Have you sent the crash reports it generates? If you don't get a crash submission dialog post a list of your components and check application events in Event Viewer to see if the crash reason is logged there.
Crash reports are written. There are some events in the application log. Where can I send it to?

 

Re: Foobar crashes repeatedly (while initialising library from NAS)

Reply #5
When the player crashes it asks to submit the crash report. Those are used to analyze common troublemakers and the Help -> Online troubleshooter menu command can then inform users about problematic setup.

If the submitted report reveals a bug in the player itself Peter will hopefully have all the required info to fix it.

If foobar2000 catches the crash and you get the dialog asking to submit crash report then Windows won't log the crash and Event Viewer will not mention any problem. But some crashes escape the internal system and they are logged by Windows. With luck the event text mentions a component that crashed by name and you can report it to the component author and possibly remove the component until it's fixed.