We’re zeroing in on the issue. Please download and test this version of MainType:
https://www.high-logic.com/tmp/maintype/MainType13.0.0.1350.exe
If that one also fails, then I would really like to have an interactive (zoom or Google meet) session to find out why it fails on your system while it runs smooth on my computer.
Erwin,
I copied 13.0.0.1350 executable over to the High-Logic MainType folder, ran the program and did the clicking and scrolling test:
No crashes!!!
I did notice that Sample window says “MainType is in safe mode and will not load fonts.”, so I double-checked FMS Config to see if was in safe mode and I was not, it’s in Normal mode, So I figure this executable has that disabled. Also, it says the FmsProxy is not running. I just thought I would state that, I am sure this is part of narrowing down the problem.
This is promising, but the part that has been disabled with this release is very complex, so I need to think about a way to isolate the problem.
Okay, I am here for you when you need me to test, Erwin.
Can you try this update:
https://www.high-logic.com/tmp/maintype/MainType13.0.0.1352.exe
You will need to store this dll in the same folder in order to run MainType:
FastMM_FullDebugMode64.dll
Hi Erwin,
I was unable to download the .dll portion of the test files.
I got this error:
" Server Error
403
Forbidden
You do not have permission to access this document."
I see. Can you download this zip file:
https://www.high-logic.com/tmp/maintype/MainType1353.zip
Then follow these steps:
Okay,
I followed your instructions, ran MainType, clicked and this time I got a “Virtual Method Called On Freed Object” error dump. I did it twice and there were two different ones, the second one was longer. I couldn’t capture the end part as it went off the screen. Let me know if you need more data from these dumps.
Did these occur where you previously had the other crashes?
No, this is the first time I got an error like this with some actual data. before it just crashes out to the desktop.
Can you try this update:
https://www.high-logic.com/tmp/maintype/MainType13.0.0.1354.exe
You need to store a copy of the DLL in the same folder. If the folder is not protected, e.g. not in C:\Program Files\High-Logic MainType but in a public folder, then after you receive an error report, it will most likely be stored as MainType_MemoryManager_EventLog.txt in that folder.
Erwin,
I copied the MainType13.0.0.1354.exe to my C:\Program Files\High-Logic MainType folder, which still contains the FastMM_FullDebugMode64.dll, and ran the program.
I did the clicking random fonts in the View window in Grid View test and I am happy to say that there is no crashing.
Of course, the Sample window and the Character window both contain the message “No Font Selected.” I assume those displays are deactivated for this test.
Interestingly, when I quit MainType I did get an error message:
Unexpected Memory Leak:
This application leaked memory. The leaks ordered by size are:
72: 3 x TB2Acc.TTBItemViewerrAccObject
It went on to say that the memory leak detail was logged to C:\Program Files\High-Logic MainType\MainType_MemoryManager_EventLog.txt, but no such file was generated (probably because that folder is protected?)
Hopefully that helps narrow this down…
It would be great if this one also works:
https://www.high-logic.com/tmp/maintype/MainType13.0.0.1355.exe
Then I am on the right track, otherwise I am lost…
Okay Wow! It works!
I copied MainType 13.0.0.1355.exe to the folder and ran the software. I can click on many fonts in the View Window and there is no crashing.
The Sample window labours to catch up, often just showing the message “Loading font.” with no displaying
The Character window does not display.
As I click around on the font titles, it hits my 12 cores of CPU aggressively:
And I should mention when I exited the software, I got the same “Unexpected Memory Leak” message.
I have now disabled only one part of the software, so try this update:
https://www.high-logic.com/tmp/maintype/MainType13.0.0.1356.exe
If this still works that would be great, otherwise I am afraid I am not able to find a solution.
Yes! This one works as well.
This time there was no “Unexpected Memory Leak” message.
The Sample window is still sluggish, and often shows the message “Loading font.” with no displaying
The Character window does not display.
That is good to hear!
It seems the problem is related to the component we use to display the character grid.
Fortunately we have a replacement for it, but it will take some time to refactor and implement it.
For now, do keep using this latest version, so we can be sure it is indeed stable.
It would be best to store both exe and dll in a general folder, like one on your desktop. Then the error report, if any, is able to save to that folder.
Okay, I took your advice and stored the folder on the desktop. Here is a sample of one of the memory leak errors:
--------------------------------2025-07-09 17:26:10.692--------------------------------
A memory block has been leaked. The size is: 72
This block was allocated on 2025-07-09 17:24:42.052 by thread 26908, and the stack trace (return addresses) at the time was:
00000000006F7C9A [Unknown function at __dbk_fcall_wrapper]
00000000006F7D75 [Unknown function at __dbk_fcall_wrapper]
00000000006D066D
00000000006C9944
00000000006D0161
00000000006DD539
00000000006DD519
00000000006D0646
00000000006D0E01
0000000000D8B48C [Unknown function at __dbk_fcall_wrapper]
0000000000D98491 [Unknown function at __dbk_fcall_wrapper]
0000000000D8AC0A [Unknown function at __dbk_fcall_wrapper]
00000000006DD539
0000000000A7A179 [Unknown function at __dbk_fcall_wrapper]
0000000000D78302 [Unknown function at __dbk_fcall_wrapper]
0000000000D77E9D [Unknown function at __dbk_fcall_wrapper]
0000000000DA1A16 [Unknown function at __dbk_fcall_wrapper]
00000000006D0E50
0000000000D89EA5 [Unknown function at __dbk_fcall_wrapper]
0000000000DA0630 [Unknown function at __dbk_fcall_wrapper]
The block is currently used for an object of class: TB2Acc.TTBItemViewerAccObject
The allocation number is: 3114155
Current memory dump of 80 bytes starting at pointer address 1E5A623A020:
60 9C D8 00 00 00 00 00 02 00 00 00 00 00 00 00 98 34 6C 00 00 00 00 00 50 EF D8 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 9A D8 00 00 00 00 00
00 00 00 00 00 00 00 00 24 F1 35 FF 9A 7C 6F 00
` . . . . . . . . . . . . . . . . 4 l . . . . . P . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . $ . 5 . . | o .
--------------------------------2025-07-09 17:26:10.701--------------------------------
This application has leaked memory. The leaks ordered by size are:
72: 1 x TB2Acc.TTBItemViewerAccObject
I hope it is not the same problem. Can you try this update:
https://www.high-logic.com/tmp/maintype/MainType13.0.0.1357.exe
To be clear, am I supposed to put this one in my new MainType folder on the desktop and run it there?
I tried this, and it does not run. No launch screen, nothing.
I get the “Windows protected your PC” message and I chose “Run anyway”, but it does not run.
Note, that I still have trhe “FastMM_FullDebugMode64.dll” in that folder.
