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)
You could look at the stacktrace to see if there are any hints to what is locking.
You can do this from visual studio 2015 community edition which are free, if you dont have another favorite debugger.
How to:
When sierra locks up
1. Start visual studio
2. From the debug menu choose "attach to process"
3. Select the sierra chart process and attach to it
4.select the call stack tab and press the pause button
5. the callstack and disassembly of where it paused
*if the disassembly doesn't show, right click on the top entry in the call stack list and select "go to disassembly"
You can continue sierra while the debugger is attached by choosing "continue" in the toolbar. You should do this several times and see if the callstack changes (To see if its locked in one specific place or is doing *something*).
If you have trouble interpreting the results you are welcome to post it here and i will take a look. (if the callstack was different on each of the "pauses", please post callstack and disassembly of top item in the call stack list for each run)
I had the same problems with Sierra Charts.
Advice from Infinity Futures help desk: replace firewall and /or antivirus program.
So I did. I replaced Commodo firewall by Windows firewall and Avast antivirus by Panda Free antivirus.
Now Sierra works flawlessly and it is much faster and reliable than Ninja Trader , which I had before.
This may be too late to help the OP, but there is also an option in the Data/Trade Service Settings to allow the server to drop data, which is set to false, but something on my end is a problem so switching that from false to true allows it to drop data when my system isn't keeping up. This has eliminated the locking up issue for me and hasn't been a problem for my trading.
For someone more serious or perhaps trading a different style that requires the best data available, this might be trouble, but it hasn't been for me. I haven't gotten any fills that were well off the charted price etc.
This is probably too late, but one thing that is not clear is whether the charts are not updating in real time or the Sierra Chart user interface is frozen. The solution is different depending upon the problem.
It is essential that a user makes this very clear when there is a "freeze" problem. This term can have many meanings and to us it means the user interface is frozen.
The user interface in Sierra Chart should not at all be frozen with that kind of configuration.
If the user interface is frozen we would suspect antivirus/anti-malware software on the system or the Global Settings >> General Settings >>Chart Update Interval is extremely low but in this last case, that is not going to cause Sierra Chart to freeze. Only possibly become sluggish at worst.
Regarding the other posts in this thread, if a chart stop updating in real time and selecting File >> Disconnect and File >> Connect to Data Feed restores the updating, then the problem was with the external Data Feed and you need to contact the provider about that problem.
That is not a problem with Sierra Chart itself. A problem like this we do hear about from time to time with Transact.
This option you refer to is CQG specific. It is a flag passed to the CQG server. Whether the CQG server does anything with it, we do not know.
Sierra Chart uses the CQG Web API and since its original release, there have been a lot of problems with this data feed, but gradually CQG has resolved them. And at the present time we are not aware of any issues of significance with it. Although it still uses an older SSL version which is considered a security risk. We also do not know why they even bother with the web socket protocol either.
And it is also very important to be very clear with us about exactly what the problem is.
If you feel you are not getting the proper help, then just ask again and be more clear about the problem.
But if it is a high CPU usage problem, ultimately you are in the best position yourself to determine what the source of the problem is based upon the information given in help topic 30. And once we know what the source of the problem is we can better help with it.