Thanks for the reply cfor, there is a lot I do not understand yet.
To explain a little more about how the application uses memory :
On startup the application malloc's memory for permanent internal tables, these are never released (except implicitly by the app exit).
For every new file, new mallocs are issued to read the file (a compressed image usually, the image is expanded),
As the file is processed new mallocs are issued for holding temporary data.
On completion of work on the file, all memory we have allocated to process that file gets released.
Permanent internal tables are retained.
It all seems to work in a multi-tasking environment on a hard machine but under VMware no.
Are you saying that the application might have used host memory for the file I/O ?
- I would have expected that to be the responsibility of the guest OS, but I could be wrong here, after all disk access from multiple guest OS's must be combined safely.
When you say "but ONLY if you have current VMware guest installed", that sounds like I am missing something.
- I thought the guest OS had to be there for the app to work, It sounds like you mean something else. Can you explain further ?
Regards
Steve