Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
We did look into it and was not able to reproduce the behaviour you experienced however, we did come across an item that did consume more memory than expected and put in a change for our next update. I am not saying that this pending improvement would change your experience.
Possible scenarios are:
- .NET runtime management (nothing we control)
- A non system indicator that eats memory
- An issue in NT
Trying to isolate of course is what is challenging. As a next step, I suggest upgrading to R5 which will release soon and see if there is any positive impact. If not, the next step would be to remove any non custom indicator to eliminate if these are the source of the memory consumption.