#75 Crash when encoding in classic mode.

[Dead1Walking]

Funny thing, it started crashing again in classic mode. Considering this is on a clean install, I'm suprised this happened at all. Nothing changed between now and when it was working as far as I can tell.
However, I am includeing the mini dump.
If you need anything else from me, let me know and I will be glad to help as best I can.
Now running Windows 10 x64 PRO
24GB RAM

[Michael Fink]

Hi Nethaniel,
thanks for your minidump. Unfortunately I couldn't pinpoint where the crash is, as the minidump contained no data segments. In the meantime I also released 2018 beta 1. Could you try with that version, too? And you could also create a full dump with this instructions, from bug #74:

You could use the Microsoft tool "Process Explorer" (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) to generate a full dump. When you see winLAME's "Crash Dump - Save results" dialog, start Process Explorer, find the winLAME.exe process, right-click the process entry and select "Create Dump > Create Full Dump...". Beware, the file may be some MBs large. If the file is too large, you may share it via other means with me (e.g. wetransfer) and send the link to vividos@users.sourceforge.net.

Thanks!
Michael

[Dead1Walking]

Ok, I downloaded the zip version of the beta, and it had no issues, however with the same files and settings 2017 crashed. I will send it via Wetransfer as apprentelly 112MB is too much here.
Update : It says it was sent.

[Michael Fink]

Hi Nethaniel,
thanks for the full dump file. It confirms that the crash was on the Classic UI's Encode page. This code was replaced by a new Encode page that using the "task manager" that is also in use in Modern UI.
I'm closing this bug. Thank you for your help!
-Michael