[x] [2344] Scheduler keeps crashing, Windows 10 64-bit

[Orator]

Just updated to the latest AIMP 5.00 build 2344 on Windows 10 64-bit and the scheduler still keeps raising exception and being auto unloaded after a crash if you try to re-load the plugin from the preferences.

Then downloaded fresh no-installer package from AIMP.ru, put it in it's own folder on different disk apart from the previously used portable version. I start the program for the first time, go straight to scheduler which opens fine, able to setup a simple sleeptimer, close the scheduler, exit program and restart, scheduler plugin raises exception and is automatically unloaded, AIMP crashes, after that restart is fine, but scheduler is unloaded.

Trying to manually re-load scheduler plugin from the preferences causes also the raised exception message in this fresh new portable version, claiming not recommended to use for stability reasons and then AIMP crashes. The build should be stable, but scheduler plugin is obviously not or some strange conflict to AIMP.runtime.dll, which also shows message on screen soon after the raised exception message.

[Soolo]

Try the debug version:
https://disk.yandex.ru/d/DY5GNMHXGfEBiw
it should generate extended report about the issue

[Orator]

Thanks! Attached is bug report from the first restart after installing portable version, successfully setting up the scheduler and exiting.

[Artem]

It seems the '.' is used as time separator on your system. So, it leads to incorrect datetime string.

[Orator]

Thank you, Artem! Changed my display language to English (Europe) that uses ":" for time separators and after Windows restart AIMP scheduler works again, no problems.

Though wouldn't it be possible to make the scheduler plugin tolerant to any Windows time separator, compliant to any display language? That would be nice user friendly solution.

[Artem]

Though wouldn't it be possible to make the scheduler plugin tolerant to any Windows time separator, compliant to any display language? That would be nice user friendly solution.

Yes, of course. I have forced to invariant format settings