The earlier log files indicate that you enter the function ForcesDraw::LoadPicture() but never exit it. This is a key finding. The program is locking up somewhere in that function.
In two separate emails, I have sent you two more test versions of pbedit.exe. (I am getting delivery failure notices for your Gmail address BTW.)
In version #2
$ unzip -l pbedit2.zip
Archive: pbedit2.zip
Length Date Time Name
--------- ---------- ----- ----
4289160 09-06-2020 06:01 pbedit.exe
--------- -------
4289160 1 file
I have added still more trace logging function calls.
In version #3
$ unzip -l pbedit3.zip
Archive: pbedit3.zip
Length Date Time Name
--------- ---------- ----- ----
4289160 09-06-2020 06:08 pbedit.exe
--------- -------
4289160 1 file
in addition to the added trace logging calls, I increased the size of an internal data structure that may be the bottleneck here.
Same deal as before. Please do the same experiments as before. Remember to
-- Ctrl+Alt+5
-- Be patient.
-- Send me the zipped pbedit.log snapshot several minutes after the point of program lock-up, without exiting the program.
I sent another email with another test pbedit.exe version #4
$ unzip -l pbedit4.zip
Archive: pbedit4.zip
Length Date Time Name
--------- ---------- ----- ----
4289672 09-06-2020 08:55 pbedit.exe
--------- -------
4289672 1 file
Same deal, do the same test with this one.
There is probably no point to your testing the version #2 that I sent earlier, so you can probably just disregard that one. Test versions 3 & 4 only for now.
I have pinpointed the line where the program locks up. It is where the program attempts to assign some memory for a new graphic object (for the newest unit's BMP image). Is it because, on your system (only?), you have exhausted memory at that point? I will have to ponder this situation, and do some researches. I will get back to you with my findings. But for now, our experiments are over. I will see what I can do.
Archived Forums
Help
Calendar
Member List
Search
){kind=link}
