Welcome Guest. Please Login or Register. Apr 1st, 2018, 05:26am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. We apologize Conforums does not have any export functions to migrate data. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
Re: LB 4.5.0 memory allocation failure
« Reply #8 on: Aug 20th, 2015, 01:19am »
Thanks for clarifying that.
RE: Quote:
I fired up Win 7 in VMWare, 1GB ram (VMWare supposed default) so it shows 2GB memory - 1 read and 1 virtual. I run a program from LBB (...) And I can run only one instance of LBB, no matter that. It just don't start.
After Win7 ends its update cycle, I was able to run 3 instances of LBB program. Then 4th said "no room". On next attempt, 4th instance run. (probably Windows just made more virtual memory - it now shows "peak" commit more then 2 GB - at 2.7) (and Task Manager shows "memory" - it says "physical memory" at 36%, Process Explorer Commit charge at 80% Empty values are 32% Task Manager and 28% Process Explorer )
After Win7 ends its update cycle, I was able to run 3 instances of LBB program. Then 4th said "no room".
That may be because you are running in a VM. This is what it says at MSDN:
"As an alternative to dynamic allocation, the process can simply commit the entire region instead of only reserving it. Both methods result in the same physical memory usage because committed pages do not consume any physical storage until they are first accessed. The advantage of dynamic allocation is that it minimizes the total number of committed pages on the system. For very large allocations, pre-committing an entire allocation can cause the system to run out of committable pages, resulting in virtual memory allocation failures."
It is this "running out of committable pages" that you are probably experiencing. In practice this is very unlikely to be a problem, but if you have specific issues (for example because you are running in a VM) what I can do is to make the amount of committed memory configurable by a setting in the INI file. Would that be helpful?
Logged
