Home >> Support Board

Support Board

Date/Time: Sat, 11 May 2024 23:29:58 +0000

How to Post a Message for Support

2093+ is causing chart studies to be changed when re-opening

View Count: 2049

[2020-06-03 08:13:47] #25 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The one known case of the out of bounds array error has been resolved in version 2115. If you are still having a problem we need to get the chart that is causing that. Instructions: Support Board Posting Information: Providing Chartbook with Only a Single Chart Also we looked further into the configuration file issue, and the circumstance that led to it is something that should not happen and really is an indication of a memory corruption. So we do not think this was the core issue but something secondary. It also does not make sense that a simple configuration file issue is going to degenerate into a stability problem on a system. That is just not going to happen. We will have a new release out in about a day but we are not certain that this is really resolving the core issue you are having. The cause of that is still unknown. And it looks like a graphics related issue based upon where the exceptions are occurring. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2020-06-03 13:41:44] #26 [Go To First Post]
samual sprat - Posts: 343
Assuming it's a GPU Issue, my graphics card (nvidia 1070) was running 80-90% all the time with Sierra. I did some experimenting and found that lowering the chart update interval reduced GPU usage. I was running at 20ms but put it to 50ms and it's still running hot around 70% usage. I really don't want to reduce it more, and it makes no sense that it would be using even 40% of my GPU for what it's doing. GPU usage was much lower before before SC 2090's, around 20% (can't remember when this changed). I guess this could lead to GPU issues if run like this for extended periods - I run 24x5 like this. Is the GPU supposed to be worked this much for opengl? I played PC Game Red Dead Redemption which is quite intensive and it uses this much GPU, but that seems logical Date Time Of Last Edit: 2020-06-03 14:03:45

[2020-06-04 22:59:25] #27 [Go To First Post]
samual sprat - Posts: 343
So I updated to 2116 this morning and on start of sierra it crashed very quickly and caused me to have to reboot. I gave it another chance without changing anything on reboot and it's been working perfectly all day today. I also decided to test out the GPU this evening by playing an intensive game, call of duty modern warefare, and it ran perfectly. No artifacts, no glitches and very smooth. Don't think my GPU is faulty, but then not sure why sierra has been the only application to cause system instability. Anyways, hopefully it's resolved now so thanks...

[2020-06-04 23:28:44] #28 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We did not do anything to resolve this, we only addressed the specific problem causing an exception upon startup of Sierra Chart with your configuration file which clearly was corrupted relating to control bar data. There may be some undiscovered problems in the OpenGL implementation in Sierra Chart, which causes a problem but any application program should not be causing system instability. If there is instability, that would indicate an operating system or driver issue. And really it is not a fair comparison to compare to another program because that programs use of OpenGL operations can be very different. Assuming that other program even uses OpenGL which it probably does not. And the other thing is that if you are not using OpenGL in Sierra Chart, then this would indicate there is still something wrong on your side because all of the non-OpenGL graphics code in Sierra Chart is completely stable. But it is important to not use custom studies and to start with a fresh global configuration file to rule out those as a problem. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-06-04 23:30:39

[2020-06-06 21:41:37] #29 [Go To First Post]
samual sprat - Posts: 343
Some errors are back again. This cannot be my hardware. I know at LEAST 5 others who are seeing the same problem as me. I'll ask them to post if needed Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340158 \| 2020-06-06 22:34:10.818 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340157 \| 2020-06-06 22:34:10.819 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340156 \| 2020-06-06 22:34:10.820 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340155 \| 2020-06-06 22:34:10.823 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340154 \| 2020-06-06 22:34:10.826 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340153 \| 2020-06-06 22:34:10.829 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69340152 \| 2020-06-06 22:34:10.830 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274615 \| 2020-06-06 22:34:10.831 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274614 \| 2020-06-06 22:34:10.832 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274613 \| 2020-06-06 22:34:10.839 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274612 \| 2020-06-06 22:34:10.841 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274611 \| 2020-06-06 22:34:10.843 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274610 \| 2020-06-06 22:34:10.846 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274609 \| 2020-06-06 22:34:10.849 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 69274608 \| 2020-06-06 22:34:10.851 Replay 3.00X: ESM0-CME 500 Volume #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-06 22:34:10.853

[2020-06-08 00:28:15] #30 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Other users can be experiencing exceptions for different reasons and you cannot know it is the same reason. It is unlikely it is the same reason. Are you using OpenGL or custom studies? More information about these is here: Sierra Chart Unexpectedly Shutting Down \| Memory Errors \| Unusual Software Problems \| Exception Errors \| Freezing of User Interface Also those exceptions relate to WM_PAINT and WM_MOUSEMOVE. We are implementing full support for out of memory conditions related to graphics when using OpenGL and also for limited cases where this potentially can be a problem when not using OpenGL. This may or may not help. Also based upon the current context and information we are not saying this is a hardware issue. It is clear that is not the case. We want you to test again on version 2119 when that is released. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-06-08 00:31:14

[2020-06-09 17:11:59] #31 [Go To First Post]
Tooth Fairy - Posts: 79
@sunnyd There could be a different exception event occurred very early on crashing everything & u see the WM_PAINT & WM_MOUSE exceptions at the end as a result of the 1st exception event.

[2020-06-09 20:28:12] #32 [Go To First Post]
samual sprat - Posts: 343
Thanks Tooth Fairy, that's true. Is there a way to know that's the case? I've just noticed that 2119 has been released, going to try it out now

[2020-06-09 20:54:25] #33 [Go To First Post]
samual sprat - Posts: 343
Still getting same error on 2119; M0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.180 ESM0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.183 ESM0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.243 ESM0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.246 ESM0-CME Rev. 2t #3 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.249 ESM0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.297 ESM0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.300 ESM0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.364 ESM0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.366 ESM0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.431 ESM0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.433 Caught an unhandled exception in c_MainMDIWindow::WindowProc. Message: 16, wParam: 0, lParam: 0 \| 2020-06-09 21:53:15.486 UPDATE FYI, I had added a third chart to the chartbook before updating to 2119 and then the error was caused. Removing the third chart in safe mode, saving the chartbook and restarting into normal mode seems to be more stable atm, HOWEVER, some of my custom studies either do not show on the chart and some are garbled. All three charts in the chartbook had market depth historical loaded with 1 day of history Reverting back to 2118 Date Time Of Last Edit: 2020-06-09 21:40:49

[2020-06-09 21:20:03] #34 [Go To First Post]
Tooth Fairy - Posts: 79
Close the chartbook will stop the continuous message pumping. It will take a while for the message log to be filled up so hopefully, u catch it in time. If u can't close it through the menu, use the X in the title bar to close it. Rollback to the 1st exception error & that's that.

[2020-06-13 10:44:33] #35 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Update: this was an incorrect conclusion: Test prerelease version 2021. We identified a problem where there was an invalid pointer being used, when more than 1000 graphics objects of a particular type were being allocated. This would be a very uncommon condition. We do not know if it is the source of the problem or not, but it is resolved. There was no problem. The pointer was always valid at all times. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-06-15 06:17:51

[2020-06-14 22:11:17] #36 [Go To First Post]
samual sprat - Posts: 343
Still getting this error in 2021 pretty much within 5s of opening my chart consistently: ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.110 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.142 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.173 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.207 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.238 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.268 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.298 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.333 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.361 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.394 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.423 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.455 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.486 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.516 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.548 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.580 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.612 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.644 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.673 ESU0-CME 10 Sec #2 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.705 ESU0-CME 500 Volume #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.735 Caught an unhandled exception in c_MainMDIWindow::WindowProc. Message: 16, wParam: 0, lParam: 0 \| 2020-06-14 23:10:25.805 Program is exiting. \| 2020-06-14 23:10:25.847 DTC Client socket (1) \| CloseSocket call. \| 2020-06-14 23:10:25.855 DTC Client socket (1) \| Shutdown started. Waiting for graceful close. \| 2020-06-14 23:10:25.856

[2020-06-14 22:27:59] #37 [Go To First Post]
samual sprat - Posts: 343
Restarted sierra on 2121 after copying charts from old chartbook to new chartbook and saving. Also reduced market depth historical back to 1 day on both charts and looks like it's working again. Will keep mdh at 1 day for now and see if 2121 is stable for a day or two

[2020-06-15 04:12:12] #38 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We still see no other conclusion other than the issue is specific to your system. Also for the record this was an incorrect conclusion: We identified a problem where there was an invalid pointer being used, when more than 1000 graphics objects of a particular type were being allocated. This would be a very uncommon condition. We do not know if it is the source of the problem or not. There was not an invalid pointer. There was not a problem to begin with. This was simply an observation that was never actually tested. Testing showed that there was a correct pointer at all times. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

To post a message in this thread, you need to log in with your Sierra Chart account: