Opened 7 years ago
Last modified 4 years ago
#4785 new defect
Memory is never given back — at Initial Version
| Reported by: | massimo ceraolo | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | *unknown* | Version: | v1.13.0-dev-nightly |
| Keywords: | Cc: |
Description
I've seen that OM (at least when used through OMEdit), never gives back memory. I understand that it uses Garbage collector, but AFAIK, at least periodically, if large amounts of memory are not allocated anymore, they should be sent back to the OS to give other processes a chance to exploit.
Steps to reproduce (OM 1.13 dev 380, win 64 bit):
1) launch OMEdit Now Task manager reports 450 MB as allocated to OMEdit.
2) load Buildings library (5.0.0: should be the latest) and double-click on Air.Systems.SingleZone.Vav.ChillerDXHeatingEconomizer
Memory reaches 3.65 GB
3) unload Buildings library. The loaded memory stays above 3.6 GB whatever you do, except closing OMEdit.
BTW, the memory used seems to be too large: Dymola for the same case uses just 235 MB total. But this is another story (see ticket #4755).
