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: Runtime Error on Quit (Read 1008 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Runtime Error on Quit

Hi guys,

My foobar is now displaying this message every time I try to quit it (see attached pic).
As a consequence, every time I start it up, I have the usual warning that it was quit in an abnormal way.

This started happening right after the following changes :
- Updated some components to their latest versions
- Updated (manually) SMP to latest version 1.5.1
- Updated (manually) foo_spotify to latest version 1.1.3
- Added a custom SMP script (please see here : https://hydrogenaud.io/index.php?topic=121277.0 )

My foobar was running perfectly prior to these changes, so I'm pretty certain that something within these changes triggered the error. Let me know if you need any more information. Thanks in advance for your help !


Re: Runtime Error on Quit

Reply #2
Just updated to 1.5.1 and can confirm I have the same crash at startup.

Went to safe mode, applied the latest dev build and problem is gone.

Re: Runtime Error on Quit

Reply #3
Thank you all. I can confirm that the error message is now gone after the SMP update.
However, fb2k still doesn't quit properly. In the Process Manager, fb2k process stays forever after quit, @ 0% CPU.

Re: Runtime Error on Quit

Reply #4
Any help on this, please ?...

In case it's useful, here is foobar2000 process stack in Process Explorer (after quit, while process is still active). Let me know if there's something else I can do. Thank you.

Code: [Select]
ntoskrnl.exe!KeSetEvent+0x6ca
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
ntoskrnl.exe!PoStartNextPowerIrp+0x1841
ntoskrnl.exe!KeWaitForMultipleObjects+0xf5d
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!NtWaitForSingleObject+0xde
ntoskrnl.exe!KeSynchronizeExecution+0x3a23
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x4a8
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64KiUserCallbackDispatcher+0x204
wow64win.dll+0x32c9e
ntdll.dll!KiUserCallbackDispatcher+0x1f
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x676
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x42a
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!EtwEventSetInformation+0x14e0c
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!ZwWaitForSingleObject+0x15
kernel32.dll!WaitForSingleObjectEx+0x43
foo_spider_monkey_panel.dll!foobar2000_get_interface+0x85e3
foo_spider_monkey_panel.dll+0x4dd86
foo_spider_monkey_panel.dll+0x53231
foo_spider_monkey_panel.dll+0x528db
foo_spider_monkey_panel.dll+0xe0847
foo_spider_monkey_panel.dll+0xddcb2
foo_spider_monkey_panel.dll+0xdb032
foo_spider_monkey_panel.dll+0xdaf23
foo_spider_monkey_panel.dll!_CreateLexer@4+0x5bf2b
USER32.dll!gapfnScSendMessage+0x332
USER32.dll!GetThreadDesktop+0xd7
USER32.dll!GetThreadDesktop+0x18a
USER32.dll!GetThreadDesktop+0x1e9
ntdll.dll!KiUserCallbackDispatcher+0x2e
foobar2000.exe+0x135c2a
foobar2000.exe+0x8ae38
foobar2000.exe+0x8b016
foobar2000.exe+0x19cc7c
kernel32.dll!BaseThreadInitThunk+0x12
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36

Re: Runtime Error on Quit

Reply #5
Also its performance graph showing that there's still something going on :


Re: Runtime Error on Quit

Reply #7
Thanks. I should mention that I have SMP 1.5.2-dev version (see attached pic for the exact version). The problem is still there.

Re: Runtime Error on Quit

Reply #8
Does anybody know when that bug will be corrected?
Alternatively, what would be the latest SMP version right before that bug?


Re: Runtime Error on Quit

Reply #10
Thanks ! :) I can wait if a fix can be expected soon (within a week or so). Otherwise it would be better for me to revert to 1.4.1.
Fingers crossed : I know that developing is a hard job !