We’ve been getting “hard” crashes on 17.1, looks like our application is using too much virtual memory.
Windows logs say crash is in kernelbase.ddl, but right before the crash there is a system event saying our app is using 58gig of virtual memory !
Attached are two screen shots, one from a test machine, one from deployed server. The deployed server has around 38gig of ram (but very little of that ram is used by 4D, mostly virtual memory). In the screenshot i tried to show the size of virtual memory, how much is ‘commited’ by mSupply (our 4d app) and how much 4D admin windows shows is used.
I’ve checked journal logs, and there is nothing out of the ordinary before the crash. Turned on 4d logs, will update when next crash happens.
There is limited/no info regarding 4D use of virtual memory, so it’s really hard to figure out.
Is there any way to force 4d to user ram before virtual memory ? Is there any way to ‘flush’ virtual memory ?
By the way, the data file is only 100mb.