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)
This has happened to me a few times recently. I've made zero changes to my DOM in months, and haven't upgraded Sierra anytime recently. But I have added other charts to my system. Resource levels are fine, I have about 20-24GB free of memory at any given time.
The issue is that suddenly out of no where (no action on my part) the DOM will just go blank, and the only solution is to restart Sierra.
When this occurs, what happens when you select Chart >>Duplicate Chart on the Trade DOM. Does the duplicated one appear properly?
Does this Trade DOM have a Trade Window attached to it?
What happens when you right-click on where the column of numbers normally appears, do you see the menu? And if you select Auto Scale the Chart DOM, do you then have a proper display?
Pretty convinced now that is the problem (2GB cap, 32-bit program)
No clue why it seems to only effect my DOM, which I didn't change. But what I have changed recently is about 20 new charts for some intermarket analysis. I'll make some adjustments to their lookback period to try and reduce memory.
So do you think the problem was due to hitting this limit (I assume yes)?
I just checked task manager again, now Sierra is using only 300MB of memory with the same workspace and has been running overnight (in other words, not freshly restarted). Not sure why it was using so much yesterday, or apparently all the previous times it kept crashing the DOM with an out of memory exception.
