0CC famitracker crashes on startup

[AfterCadaver]

It started when I was working with famitracker consistently for several days(albeit with the app crashing upon first startup, showing complete stability the next time) until one day it crashed without being able to startup at all after that.

I will attach the dump file

Problem signature:
Problem Event Name: APPCRASH
Application Name: 0CC-FamiTracker.exe
Application Version: 0.3.15.3
Application Timestamp: 5b0137b0
Fault Module Name: 0CC-FamiTracker.exe
Fault Module Version: 0.3.15.3
Fault Module Timestamp: 5b0137b0
Exception Code: c0000005
Exception Offset: 002bbf17
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 9c4d
Additional Information 2: 9c4d7b7f5e9f54392035636c9c97d5fa
Additional Information 3: d05d
Additional Information 4: d05dd97924a4d0a7e4d0f91c4fafb9b1

[blw043]

Can reproduce. 0ccFT v0.3.15.3 and v0.3.14.5 fail to start up on Windows 10, v17763.195 (latest as of this writing). It seems the latest round of Windows updates broke something, v0.3.14.5 worked perfectly last weekend, and the update was the only major change to my system since then.

It hits a null pointer at 0x006bbf17. The asm instruction is mov eax, ds:[edi]. Without symbolic info I can't figure out much else.

Dump files are attached.

MiniDump_20181221-2134-v0_3_15_3.zip

MiniDump_20181221-2111-v0_3_14_5.zip

Update: I managed to build the source with VS2017. It seems CPatternEditor isn't getting its DCs initialized properly.

Update: The null DC issue was caused by a multi-monitor issue. I had connected my laptop to a second display, had 0ccFT open on the second display, closed 0ccFT and disconnected the display. Afterward, 0ccFT was attempting to restore its window position to the nonexistent second monitor, was trying and failing to create DCs for that display, and crashed. I may open a new issue for this.

[AfterCadaver]

I've encountered the problem again with a new computer.

0cc famitracker.zip

[nyanpasu64]

Closing 0CC with the entire pattern editor below bottom of screen saves the window position to registry. Restarting 0CC then crashes. For a workaround, try deleting registry key HKEY_CURRENT_USER\Software\0CC-FamiTracker\Window position?

[oscwav]

I found a solution. Just open registry edit (regedit) go to hkey current user, go to software, delete the folders 0cc famitracker and famitracker. And next time when you open 0cc famitracker make sure the window is maximized or moved to a diffrent location than default.