search

BartmanAbyss / vscode-amiga-debug

One-stop Visual Studio Code Extension to compile, debug and profile Amiga C/C++ programs compiled by the bundled gcc 12.2 with the bundled WinUAE/FS-UAE.
GNU General Public License v3.0
314 stars 39 forks source link

endcli CloseWorkBench pair doesn't free up any memory #48

Closed rjobling closed 3 years ago

rjobling commented 3 years ago

I thought I would try endcli/CloseWorkBench to free up some chipmem on the A500 config.

However, it didn't seem to improve how much memory I can allocated with AllocMem(... , MEMF_CHIP). The largest size I can allocate is 427k in both cases.

Am I doing something wrong or is that to be expected?

I vaguely remember that kick1.3 might not close the workbench all the way.

Is there any other way to improve the chipmem I can allocate?

BartmanAbyss commented 3 years ago

I never tried myself. Did you compare the numbers AvailMem(MEMF_CHIP|MEMF_TOTAL) returns (instead of MEMF_LARGEST? Maybe the additional memory is just not continuous? See here

rjobling commented 3 years ago

That should have occurred to me!

So, it does work, it's just slightly annoying!

Before Chip Avail: 438184 (438184 largest) Fast Avail: 452264 (443304 largest)

After Chip Avail: 479272 (438184 largest) Fast Avail: 453496 (443304 largest)