Login Page - Create Account

Support Board


Date/Time: Tue, 25 Feb 2020 08:56:51 +0000



SC 2021 Crashing on mouse wheel scroll over quote board

[2020-02-12 06:50:45]
joshtrader - Posts: 341 | Ending Date: 2020-08-26
SC is crashing when I do the following. Note that these are the steps to reproduce the bug. Note that in my existing chartbook, I don't need to do the following, it just happens, but the below can be used to reproduce:

1) Start SC
2) Connect to the data feed
3) With no chartbook loaded, File->New Quote Board
4) Load symbol list (any one will do, as long as it's enough symbols to create a vertical scrollbar and horizontal scrollbar
5) Drag the right side of the window to a width so that the horizontal scrollbar disappears
6) Drag the bottom of the window down so that the vertical scrollbar disappears
7) Hover anywhere in the quote board window and scroll using the mouse wheel

I inadvertently crash SC by accidentally scrolling my wheel when over the quote board at least 2-3 times a week. Until now I thought I was doing something incorrect, but now I know that the above is definitely causing the bug.
[2020-02-12 07:06:39]
Sierra Chart Engineering - Posts: 81442 | Ending Date: 2020-06-09
Quite sure this has already been resolved. Update to the current version:
https://www.sierrachart.com/index.php?page=doc/SoftwareDownload.php#FastUpdate

And also, the problem really was at the operating system level. Something trivial like this should not have been causing a problem to begin with.

And we are not able to reproduce this on the current version.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2020-02-12 20:08:25]
joshtrader - Posts: 341 | Ending Date: 2020-08-26
Unfortunately, this is occurring even after updating to the most current version, 2048. The easiest workaround is to force a vertical scroll bar, and this will be a sufficient workaround for the time being.
Date Time Of Last Edit: 2020-02-12 20:09:25
[2020-02-12 20:45:16]
Sierra Chart Engineering - Posts: 81442 | Ending Date: 2020-06-09
The more time that goes by and the more that we work with Windows we just realize how bad it really is. The exception problem is occurring at the operating system level for no reason at all.

We will make an educated guess as to why we think this is still happening in your case and we will implement a solution in the next release.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2020-02-14 23:39:50]
User816220 - Posts: 23 | Ending Date: 2020-03-13
I had the same issue: https://www.sierrachart.com/SupportBoard.php?ThreadID=47163

In version 2048, SC crashes with OpenGL disabled but doesn't crash with OpenGL enabled.

In version 2050, I'm still seeing the crash with OpenGL disabled. The message log did pop up just before the crash:

Caught an exception in c_ListBoxWindowBase::WindowProc. Message: 522, wParam: 18446744073701687296, lParam: 41027244| 2020-02-14 17:47:31.166 *

I attached the debugger output from 2050 showing the stack trace.
attachmentwindbg.txt - Attached On 2020-02-14 23:38:30 UTC - Size: 528.32 KB - 5 views
[2020-02-15 04:36:33]
Sierra Chart Engineering - Posts: 81442 | Ending Date: 2020-06-09
We are puzzled by this because clearly what that attachment shows is there is a stack overflow which would indicate a problem on the Sierra Chart side. But yet we put a specific safeguard in for a stack overflow and cannot see how it can even occur especially being that we are confirming based on message 522 that it is a scroll wheel message event.

So not really sure about this at this point. And we still cannot reproduce it at all.

This may be some Windows issue triggering the stack overflow but it should not even be occurring.

One question about post 5 is do you have visible scrollbars on the Quote Board, either horizontal or vertical or both, when using the scroll wheel? We need more information. Does the presence or no presence of scrollbars cause the problem. Now we know this was answered in the first post but we are asking about post 5.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2020-02-15 04:38:14
[2020-02-15 08:23:00]
Sierra Chart Engineering - Posts: 81442 | Ending Date: 2020-06-09
See if you still have this problem in prerelease version 2051 which has been released.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2020-02-15 20:39:54]
User816220 - Posts: 23 | Ending Date: 2020-03-13
I only see the crash when neither scrollbar is visible. No crashes with just one or both visible.

I tried 2051 and saw the crash with:
- Desktop, Win7 (existing install), SC (existing install), nvidia graphics
- Desktop, Win10 (clean install), SC (clean install), intel graphics
- Laptop, Win10 (existing install), SC (existing install), amd graphics

On my end, the only difference I've found between crashing and not crashing is enabling OpenGL for chart graphics. I didn't see any crashes with OpenGL enabled on the three systems above.
[2020-02-16 11:42:26]
Sierra_Chart_Engineering - Posts: 534 | Ending Date: 2020-11-26
We have fixed the problem. Can you tell us what kind of mouse wheel you are using? We want to know the model of the mouse/pointing device.

Based upon the solution, this does appear to be a problem at the operating system level or within MFC. Sierra Chart was not doing anything wrong but we made a completely trivial change that fixed it.

We are putting out version 2052 in about 5 minutes.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation
Date Time Of Last Edit: 2020-02-16 11:42:54
[2020-02-16 12:44:20]
User816220 - Posts: 23 | Ending Date: 2020-03-13
Thank you, 2052 fixed the issue.

I saw the crash with 2 Logitech MX518s (original version, about a decade old), and a Lenovo EMS-537A. I also saw it doing two finger scrolling on an ELAN touchpad and a Synaptics touchpad.
Date Time Of Last Edit: 2020-02-16 12:46:00
[2020-02-16 17:58:58]
User379468 - Posts: 258 | Ending Date: 2020-02-29
I did not know reason but also had this crash for awhile on Logitech G502 mouse scroll, seems fixed on v2052 so far.
[2020-02-16 18:11:02]
User664240 - Posts: 33 | Ending Date: 2020-03-18
FWIW Identical issues as above Log. MX310
and repaired with ver.2052
[2020-02-16 20:23:05]
Sierra Chart Engineering - Posts: 81442 | Ending Date: 2020-06-09
We tested for the problem using a Dell touchpad using two finger scrolling with a Synaptics driver and could not reproduce the problem. We also tested with mouse wheel events across a Remote Desktop connection. Still not a problem. It was not until we used a Logitech pointing device (mouse) with a scroll wheel where we then were able to reproduce this.

Basically what seems to have been happening was that Sierra Chart was not processing the mouse wheel message and indicating it did not process it, when there were no scrollbars but then apparently the message was just getting passed around continuously between lower-level MFC and operating system functions leading to a stack overflow.

So what solved the problem is just that in all cases Sierra Chart now indicates the mouse/scroll wheel message is processed. It should have been that way, but really it was not regarded as a mistake indicating it was not processed.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2020-02-16 20:29:14
[2020-02-16 22:49:32]
Sierra Chart Engineering - Posts: 81442 | Ending Date: 2020-06-09
Actually upon reviewing the code further we do see where in the Sierra Chart code there was a problem. Sierra Chart would receive the scroll wheel message in the parent window and then pass it to the child window and then the operating system was passing it back to the parent if Sierra Chart indicated it was not processed, causing an endless loop.

The problem is that this behavior with the message being passed back up to the parent is nonstandard. It is not something we normally see with window messages. So it was unexpected and furthermore, the problem was never reproducible until we used a Logitech pointing device.

From Microsoft documentation:
The DefWindowProc function propagates the message to the window's parent. There should be no internal forwarding of the message, since DefWindowProc propagates it up the parent chain until it finds a window that processes it.

But it really is not quite this simple because at the point of the original processing Sierra Chart did always indicate the message was processed. And that is why we think it was not reproducible.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2020-02-16 22:50:39
[2020-02-17 05:49:14]
joshtrader - Posts: 341 | Ending Date: 2020-08-26
That's a tough one you guys solved .. dependent on the type of mouse? Yikes. Great job and thank you, I have confirmed that this is fixed on my machine as well, and yes, I'm using a logitech mouse.

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

Login

Login Page - Create Account