• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

scenProc v1 not releaseing memory

MyPC8MyBrain

MyPC8MyBrain

Messages
596
Country
us-california
Hi Arno
Ive been running some large jobs on my end past few days; using v1 since you've released it;
the one thing i have noticed; scenProc doesn't release physical memory at the end of the run;
even if a new job is started; memory is still not released unless scenProc manually closed first;
if its sitting idle at the end of a job, all used memory is still allocated to scenProc
is this by design?

its very noticeable with large jobs, in my case 15+GB are locked at the end of the job
(job has completed successfully; all expected output files are accounted for)
 
Last edited:
Hi Chris,

It should behave the same as the development releases before, I haven't changed how memory is handled.

But I think it's .NET behavior to not always release the memory, even if the objects are removed. Don't think I can do much about that.
 
Thank you Arno,
im pretty sure i have the latest .NET
although thinking back; it seem to have started closely to when i installed Visual Studio 2013 community edition few weeks ago;
before that i never had this behavior with scenProc even with pre v1 releases
 
And what does the latest development release do, same behaviour?

Installing visual studio should not influence how scenproc works.
 
i know installing VB shouldn't affect scenProc;
but its the only common denominator i could think of,

the behavior was very much the same as it is now;
scenProc completes the job successfully; while memory consumption remains at its last peak; and not freed until scenProc is closed then started again,
i should mention that i am on win7 ENT SP1 x64 with .NET 4.5.1 (i will snap a screen shoot in few hours)
 
I'll double check here, but nothing has changed on the code that affects the memory after running.
 
since i have the ram, i didn't run the job in batch mode;
it takes a very long time to complete; im on the edge only towards the end;95% time i still have plenty ram to spare,
i don't think the job enters paging state; i still have almost a full 1gb free before the job completes;
last job (150,000 AGN files produced) ended with 15.1gb global consumption; scenProc was just holding 14gb of that,
 
here it is

Completed.jpg
 
Hi,

I finally had some time to look at this. I think this problem must have been in the development releases for a long time as well. But I have now improved the memory cleanup after scenProc finished running. So it should return the memory must better now. The change will be in the next development release as usual.
 
You must log in or register to reply here.
Back
Top