| View previous topic :: View next topic |
| Author |
Message |
skynet888 !BEWARE! Deletes post on answer
Reputation: 1
Joined: 12 Apr 2021 Posts: 68
|
Posted: Tue Dec 30, 2025 8:02 pm Post subject: CE7.5 unresolved bug: An extra deinitialization is repeated |
|
|
Cheat Engine 7.5 unresolved bug: An extra deinitialization is repeated during the next scan.
https://b23.tv/oB3S1Vg
|
|
| Back to top |
|
 |
Dark Byte Site Admin
Reputation: 471
Joined: 09 May 2003 Posts: 25840 Location: The netherlands
|
Posted: Wed Dec 31, 2025 9:28 am Post subject: |
|
|
it's not in english ,dutch or german, so I can't follow, so explain what the issue is. The video just shows someone being obsessed with the double deinitialize but doesn't seem to show any issue
foundlist deinitialize can be called multiple times unless you've made some modifications elsewhere and rely on the info in the foundlist
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
 |
skynet888 !BEWARE! Deletes post on answer
Reputation: 1
Joined: 12 Apr 2021 Posts: 68
|
Posted: Wed Dec 31, 2025 7:03 pm Post subject: |
|
|
| Dark Byte wrote: | it's not in english ,dutch or german, so I can't follow, so explain what the issue is. The video just shows someone being obsessed with the double deinitialize but doesn't seem to show any issue
foundlist deinitialize can be called multiple times unless you've made some modifications elsewhere and rely on the info in the foundlist |
He means that "deinitialize has already been executed once in the "first scan", so these two lines of code in the "next scan" should be commented out; otherwise, deinitialize will be executed twice, which affects program performance."
He said, "CE7.5 still hasn't fixed this bug."
| Description: |
|
| Filesize: |
228.03 KB |
| Viewed: |
288 Time(s) |

|
|
|
| Back to top |
|
 |
Dark Byte Site Admin
Reputation: 471
Joined: 09 May 2003 Posts: 25840 Location: The netherlands
|
Posted: Thu Jan 01, 2026 1:45 am Post subject: |
|
|
it's only double for memscan objects that have an OnScanStart defined and in that OnScanStart deinitialize is called (only mainform memscan, and custom lua memscan code that has it set explicitly)
it happens in tmemscan.nextscan which is an initializer for a scan, so runs only 1 time during a scan. And deinitialize only frees handles and memory when it is available. If it's not there in the 2nd run, it gets skipped. There's no noticable performance hit
this is not a bug or an issue
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
 |
|