Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 20 May 2024 01:15:57 +0000
Post From: Memory Leak on Windows 7
| [2019-03-05 13:53:49] |
| User75002 - Posts: 117 |
|
Hello, I am experiencing what I believe is a memory leak in Sierra running on Windows 7 in a VirtualBox environment. Background: Over the weekend I rebuilt my Windows 10 system with Linux and am using VirtualBox to run a Windows 7 64bit system for Sierra. Windows 7 was given 4vCPU and 8GB memory. On Windows 10 I was running 1875 and on the Windows 7, I installed the latest 1880 version. Since then I have had my memory usage slowly increase, more so when the market data volume increases or maybe just when I am more actively using it. On initial reboot and load of Sierra, Sierra claims to use about 250MB and total system usage is about 1.5GB. Last night, I looked at my total system memory usage after running all day and it was at 4.3GB, but Sierra was only showing 270MB. I then closed Sierra and the memory went from 4.3GB to 1.5GB. When I started Sierra again, I noticed the memory jumping around between 1.8GB and 3.8GB. I never noticed this on my Windows 10 system. After the chartbooks were opened and data downloaded, it returned to 1.8GB. This morning (7am EST), I looked at the system and it was at 2.3GB. About an hour later (8:30am EST now) after I went through and looked at the charts for the morning, it is at 3.3GB. Nothing else is on this computer except for the Gain Capital OEC platform. I don't know if this is an issue with 1880, Windows 7 or it running under VirtualBox, but would like your input and thoughts, maybe some things to try to isolate further? I will try to roll back to 1875 now and see if I continue to have the problem throughout the day. When I closed Sierra to roll back my memory usage went from 3.3GB to 1.3GB. After rebooting and starting 1875, my memory went from 900MB to 2.8GB. I will play around with closing some chartbooks to see if one of them may be corrupted and update the post later. Kind Regards, Kevin |