ptitSeb
ptitSeb
The memory error are some bug in box32 certainly. There are still some bugs in box32, and finding them is harder and harder. As for the long conversion: yes, that's...
Yeah, steam is also unstable. That's still box32 issues that need to be found and fix.
There is some work going on to reduce memory, be patient.
Block lifetime is a complicated mater. I did some experiment to free unused block but that wasn't very conclusive. By design, blocks can be chained internaly: with the jumptable mecanism....
The issue here is that to be able to free old/unused block, you need to make sure blocks are not in-use anymore. The counter you added is only good to...
Note that I will probably work on this subject very soon. A first implemention, with limitation, but enough to already see reduced memory footprint when activated.
> Great to hear that you’re already working on an initial implementation. I can help on complementary areas — for example, evaluating different cache-replacement policies, validating the heuristics with profiling...
I guess this ticket is fine unless you want more realtime discussion.
pushed a first implementation there: https://github.com/ptitSeb/box64/commit/81b080eb5d5dd2a23e5b952d11efea24bfe4c2fa
The of_convert message is probably harmless. Try to add `BOX64_DYNAREC_STRONGMEM=1` to avoid the freeze. Also, it's a good practice to close a ticket when the issue is fixed, and open...