Home >> Support Board

Support Board

Date/Time: Tue, 23 Apr 2024 22:35:37 +0000

How to Post a Message for Support

OpenGL Exception/Stability Issues

View Count: 4323

[2020-06-19 07:51:20] #50 [Go To First Post]
samual sprat - Posts: 343
@nosast thanks bud, very much appreciated I too use a lot of drawing tools, lines, channels, transparent rectangles and also copy drawings across charts. Zooming often seems to cause crashes, but only when I first open the chartbook. Like you if I leave it alone for a min or two it will be stable for days I mainly get issues after updating to a new version of SC, after which to get it stable I find copying charts in safe mode to a new chartbook fixes most crashing issues. Seems we need to get a list of things that cause issues for people and compile it somewhere so we can find patterns

[2020-06-22 16:58:02] #51 [Go To First Post]
nosast - Posts: 290
I did lot's of testing but the only thing I'm pretty sure is, that when I don't have any chart drawings on this particular profile chart SC is stable. Otherwise it crashes when doing some basic graphics work line moving lines or so. Also when I start Sierra and first thing is to zoom/unzoom this chartbook it SC crashes. Problem really seems to be with "chart drawings from other charts". Not happy but don't know how to drill it down further. Any help appreciated! LOG: Chart #4 has tagged chart #1 for full recalculation. Chartbook: Moneyflow.cht \| 2020-06-22 11:52:53.305 ESU20_FUT_CME [CB][M] 2 Min #1 \| Performing a full recalculation because it has been tagged. Chartbook: Moneyflow.cht \| 2020-06-22 11:52:53.857 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.730 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.735 ESU20_FUT_CME [CB][M] Aligned Renko 5t #12 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.736 ESU20_FUT_CME [CB][M] 1 Sec #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.737 ESU20_FUT_CME[M] #11 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.751 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.766 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.799 ADV-SP[M] 15 Min #14 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.799 ESU20_FUT_CME [CB][M] Aligned Renko 5t #17 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.800 ESU20_FUT_CME [CB][M] 50 Trades #5 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.801 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.830 ESU20_FUT_CME[M] #11 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.860 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.876 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.908 ESU20_FUT_CME [CB][M] 15 Min #6 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.925 ESU20_FUT_CME [CB][M] Point & Figure 1-25 #16 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.927 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:54.938 ESU20_FUT_CME [CB] 60 Min #9 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-22 11:52:5

[2020-06-22 20:10:26] #52 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We have tested three instances of this Chartbook (We made copies of it): ES_REPLAY.Cht in the same installation of Sierra Chart now going on more than a week, complete stability. We have reloaded the charts multiple times. We have rolled over to the September contract, we have done replays, we have done various things to create heavy CPU load by compressing the scale of the Market Depth Historical Graph and reloading charts simultaneously. 100% stability. We have the exact opposite impression whereby we see just how fast and stable the OpenGL implementation in Sierra Chart is. We are going to continue to test and add in additional Chartbooks in this thread and test them all simultaneously. 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-23 04:02:29

[2020-06-22 21:06:51] #53 [Go To First Post]
nosast - Posts: 290
@SC: I don't know which chartbook you are refering to but have you also tested with graphics like horizontal lines and extending transparent rectangles that are referenced from another chart? As stated in #49, without graphics from another chart it seems to be stable or at least I could not reproduce the crash. With the referenced graphics I can always reproduce it. I don't see high CPU or GPU load and OpenGL is running perfect. Pretty sure these crashes are just happening when working with the chart like preparing for the day. Also if I start up Sierra and zoom/unzoom this chart before the referenced lines appear it very often crashes/freezes. (chart update interval on my profile chart is at 10.000 ms. Conclusion: Zooming and/or copying/moving Lines/Zones that are referenced produce these freezes at least for me. Thanks that you reconsidered to look into this issue! Date Time Of Last Edit: 2020-06-22 21:10:26

[2020-06-23 02:23:20] #54 [Go To First Post]
zippyzip - Posts: 293
fwiw biggest issues have come from using diff bar types and historical depth . just adding to the list !!!

[2020-06-23 04:00:18] #55 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are referring to the Chartbook entitled Crash_Chartbook1. And we have tried extending rectangle drawings and horizontal line drawings copied to other charts. Also it makes no technical sense why When using OpenGL a problem would be encountered when working with copied drawings. That would be just a random situation due to apparent memory corruptions going on in your case. We still have encountered zero exceptions and no problems at all. Sierra Chart is completely stable without any exceptions. Post # 54 provides no useful information. 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-23 04:00:38

[2020-06-23 07:51:07] #56 [Go To First Post]
nosast - Posts: 290
Attached are my two chartbooks. I have no drawings in the chart (crash) itself but they are referenced from another chartbook (master). I need this setup as this master gets synced across two of my workstations via dropbox. I'm not 100% sure if these references are causing this issue but without these it seems stable. Could also be a problem with the aggregation to 4 ticks in the volume profile. Zooming the chart with arrow keys and/or working with drawings cause the exception. When I just leave it running - it's stable for days. Date Time Of Last Edit: 2020-06-23 12:30:23


crash_cb.Cht - Attached On 2020-06-23 07:50:55 UTC - Size: 3.56 KB - 336 views master_cb.Cht - Attached On 2020-06-23 07:51:01 UTC - Size: 3.28 KB - 343 views

[2020-06-23 13:33:10] #57 [Go To First Post]
Tooth Fairy - Posts: 79
@nosast I'm going to try your 2 chartbooks cuz I couldn't duplicate the exceptions on the other one & they could never find my exceptions using safe mode. At least, your chartbook has no custom studies so there is hope that we all meet there. lol.

[2020-06-23 13:45:28] #58 [Go To First Post]
ejtrader - Posts: 688
@nosast - I checked it on my system and did run into the windows exception issues that you have reported - I just used the chartbooks as they are and didn't use any drawings etc) (have NVIDIA 2080 super). On the master chart used the chart scroll few times and it has generated windows exceptions.

[2020-06-23 14:17:23] #59 [Go To First Post]
Tooth Fairy - Posts: 79
ESU20_FUT_CME [CB][M] 60 Min #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 \| 2020-06-23 14:13:00.125 * @nosast - It does generate exceptions on my test using 2 chart books above by zooming (using arrow key) on the master. I didn't change anything. Fresh install 2125 on a different directory for testing purposes only. Nvidia 2070 Super. PS: Anyone who has AMD/Intel graphic card wants to try nosast's charts above to see if it can generate exceptions? Date Time Of Last Edit: 2020-06-23 16:22:39

[2020-06-23 14:59:53] #60 [Go To First Post]
nosast - Posts: 290
@Tooth Fairy @ejtrader Thanks guys for validation! Hopefully this helps SC engineers to find the root cause! Date Time Of Last Edit: 2020-06-23 15:33:47

[2020-06-23 21:53:31] #61 [Go To First Post]
ertrader - Posts: 644
I loaded your master cb only and began getting cpu exceptions. I did nothing but try to open the chart. ESU20_FUT_CME [CB][M] 60 Min #1 \| Caught an unhandled exception in c_Chart::WindowProc. Message: 512, wParam: 0, lParam: 1966879 \| 2020-06-23 17:46:23.990 This is on my Windows 10 computer I use for testing: Intel i7-8550U 1.8 GHZ 16Gig Ram SC 2125 64 Bit OpenGL Intel UHG Graphics 620 Built-in Windows 10 V1909 OS build 18363.900 Home version Date Time Of Last Edit: 2020-06-24 20:22:08

[2020-06-23 22:50:39] #62 [Go To First Post]
nosast - Posts: 290
@etrader You only openend the master chartbook and got exceptions, right? The only thing „special“ is the aggregation to 4 ticks in the VbP study. That means it has nothing to do with referenced drawings and is also not caused by nvidia specific drivers. Did you also test in GDI?

[2020-06-23 23:08:14] #63 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are testing the Chartbooks post #56 now. We are now testing 6 Chartbook simultaneously. No exceptions so far for more than a week. Everything stable. And yes we do do frequent interaction with the charts by doing the following: -Reloading them (Edit >> Reload All Charts) -Changing scales -Adjusting drawings both on source and destination -Rearranging the charts through tile operations. 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-23 23:15:06

[2020-06-23 23:31:11] #64 [Go To First Post]
ertrader - Posts: 644
@nosast Yes, that was the only chart I opened. All I had to do was open it and CPU exceptions occurred. First time opening and it was trying to load 120 days of data, it started producing dozens of CPU exception error messages without stopping. When I loaded again, it seemed to start when I tried to scale or move to prior days but it happens after loading data. Also, I did not have to do F11 for data connection. I just now tried loading as GDI and received NO CPU exceptions and am able to move to prior days and rescale with no problem. Definitely OpenGL related and reproducible on my computer each time. Still working only with the master chart. Date Time Of Last Edit: 2020-06-24 01:30:14

[2020-06-24 20:09:04] #65 [Go To First Post]
nosast - Posts: 290
@SC Still no exceptions on your system with my example chartbook when loading / zooming or interacting with the chart? Are you also testing on a current Win 10 Pro Release? I'm running: Intel i7-9700k 16G Ram SC 2125 64 Bit OpenGL Nvidia Quadro P600 with latest nvidia drivers Windows 10 V1909 OS build 18363.836 Date Time Of Last Edit: 2020-06-24 20:09:26

[2020-06-24 20:21:31] #66 [Go To First Post]
ertrader - Posts: 644
Mine is Windows 10 Home

[2020-06-25 00:58:14] #67 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We finally today encountered the exception on a WM_PAINT event, when modifying a chart drawing. This is after hundreds of modifications previously done without an issue. So now that we have this one case, we need to go through the process of isolating where it is occurring. This is not going to be easy and will take time. Allow about a week. We will try for sooner if we can. But it can still take longer for us to fully understand the issue and develop a solution. So we really in the end cannot give any specific timeframe as to how long this will take. At this point we do not need any further information, so it is not going to help to post further in this thread. 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-25 00:59:15

[2020-06-25 06:48:57] #68 [Go To First Post]
nosast - Posts: 290
@SC Glad you found the issue. Just as an addition re your statement "... after hundreds of modifications...". I can reproduce this issue without even touching the drawings by just zooming with arrow keys when SC just loaded the chartbook. It may be the same cause as I have some drawings referenced in the chartbook and maybe pulling this from another chart counts as a modification.

[2020-06-25 07:12:31] #69 [Go To First Post]
Sierra_Chart Engineering - Posts: 14064
We have not found the issue. We are only able to reproduce just one time. It could still be days, or weeks before it is narrowed down. 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, use the Teton service: Sierra Chart Teton Futures Order Routing

[2020-06-27 11:39:46] #70 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Test prerelease version 2128. We did find a problem that has been resolved. There was access out of range in a vector. It was a very rare occurrence to reproduce the issue because it occurs on very specific condition when Sierra Chart draws in several windows and Sierra Chart switched drawing context when OpenGL pipeline is full. 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-27 12:39:41] #71 [Go To First Post]
ertrader - Posts: 644
On my Windows 10 test computer with V 2128, I am no longer seeing CPU exceptions for the master_cb chartbook.

[2020-06-27 14:05:03] #72 [Go To First Post]
nosast - Posts: 290
On 2128 I also could not reproduce the issue. Fixed! Thanks!!

[2020-06-27 16:00:03] #73 [Go To First Post]
Tooth Fairy - Posts: 79
On 2128, I couldn't reproduce exceptions on nosast's chart. I'm testing our charts now. So far so good. My experience shows me that in our case, it could run many days w/o producing exception then kaboom. Just hope that is the same issue. Date Time Of Last Edit: 2020-06-27 16:02:57

[2020-06-29 22:06:16] #74 [Go To First Post]
User929084 - Posts: 60
On 2128 I don't get exceptions anymore as I used to. By this time I would already get exceptions and SC would crash. Looks good so far.

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