Online Radio http://online.radiorecord.ru:8102/mdl_128
Code: C0000005h, flags: 00000000h, address: 77596A0Ch
Access violation, operation: read, address: 00000014h
Code bytes (77596A0Ch):
775969CCh: E1 3F 80 F9 3F 0F 84 50 50 04 00 0F B6 CA 83 E1
775969DCh: 3F 8D 04 FD 00 00 00 00 2B C1 5F 5E 5B 8B E5 5D
775969ECh: C2 0C 00 8B D0 C1 EA 03 33 10 33 15 B4 17 66 77
775969FCh: 33 D6 66 85 D2 75 0F C1 EA 0D 8B C8 2B CA 8B 09
77596A0Ch: 66 8B 49 14 EB 9C 33 C9 EB F6 0F B7 08 EB 93 81
77596A1Ch: F9 FF FF FF 7F 77 12 64 A1 30 00 00 00 51 6A 00
77596A2Ch: FF 70 18 E8 CC B4 FE FF C3 33 C0 C3 8B FF 55 8B
77596A3Ch: EC 83 E4 F8 83 EC 14 53 8B DA 8B D1 56 57 89 54
EAX: 17BAB198, EBX: 17BAB1A0, ECX: 00000000, EDX: 907FB25B
ESI: 015D0000, EDI: 00000000, EBP: 011FEDEC, ESP: 011FEDD8
Symbol: "RtlSizeHeap" (+ECh)
OS: Windows 10.0.17763 x64
CPU: Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz, features: MMX SSE SSE2 SSE3 SSE4.1 SSE4.2
CPU threads: 4
Audio: TX-SR608 (Аудио Intel(R) для дисплеев); Динамики (Bluetooth Audio); Динамик (Conexant HD Audio)
Thanks for the report.
You appear to have plenty of known bad components running.
Please get rid of them and try again.
Tried this radio with a clean 1.4.3 install, no crashing occurred.
Works for me too on not-so-clean 1.4.3 installation.
One other thing.
I don't know why people do this, maybe you can enlighten me, because there's plenty more of the same on the crash report tracker.
You have the latest foobar2000.exe, new FFmpeg, but other DLLs from OLD foobar2000 versions.
Under no condition the foobar2000 installer does that. Did you mix binaries from different foobar2000 releases manually?
Mixing binaries from different releases of some program is generally asking for trouble. These are not optional components for a reason. In particular, foo_input_std.dll expects the same FFmpeg version that it was compiled against, which is probably the direct reason for your crashing.
I specifically made foo_input_std.dll & foo_ui_std.dll report the version number of the foobar2000 release that they came with to troubleshoot these cases. The ones you have predate this change, so they're obviously not from fb2k 1.4.3.