Community forum

Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
View
Go to last post Go to first unread
Offline Support  
#1 Posted : Tuesday, December 29, 2015 12:17:45 PM(UTC)
Support

Rank: Official support

Joined: 12/1/2015(UTC)
Posts: 146

Thanks: 16 times
Was thanked: 6 time(s) in 5 post(s)
VisualCron is written in a .NET-language. Programs, which run under the .NET Framework have different memory handling. The memory handling is called Garbage Collection and it's handled automatically by the .NET Framework. When starting a .NET-application, the .NET-Framework allocates some memory, often more than needed. Memory is automatically freed when no longer needed by the application. Freeing memory takes system resources and is nothing that you want to do all the time.

Often only memory is freed when it's really needed. This may result in that a .NET application may appear to use more resources than it really do. The bottom line is that you don't have to worry about this as long as an application does not increase in memory in regular intervals - then it may be a problem (memory leak).
Michael
Support
http://www.visualcron.com

Please like VisualCron on facebook!
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Scroll to Top