Support Board
Date/Time: Wed, 15 Jan 2025 17:47:50 +0000
Post From: Warning: Caught an exception during the processing of a timer event
| [2017-07-17 03:20:13] |
| |
|
Clearly I'm not but SC is truncating the chartbooks anyway.
This is completely impossible. Sierra Chart will not save part of a Chartbook. It has no such functionality for that. We do not trust what you are saying based upon your previous postings. Nobody has such a problem. Absolutely nobody has a problem like this when they do not save the Chartbooks. and still ended up with around 10+ chartbooks that had written out the initial SC_CHART_BOOK header and only that stream of bytes. Maybe you have enabled the option to automatically save Chartbooks. SC still remains in this broken state and just catches exceptions on timer events and logs them, forever.
In regards to your other statements, primarily what you are describing is the consequence of the concept of the exception. These exceptions are thrown by the operating system and MFC and STL. We have no control over this. It is not possible for us to catch all of these at the point where they occur. That would be ridiculously complicated and problematic. And there is no way we could possibly catch them all. This is what makes the exception concept so insanely stupid and we totally disagree with them. They put the program into an uncertain and unreliable state with a wild jump of execution to a different location. All significant memory allocations are gracefully and properly handled. And all memory allocationss done by our own string class are properly handled. And gradually we are migrating all strings to our own new class. Basically your statements demonstrate overwhelming ignorance as to the problem that a program developed for the Windows operating system and MFC and STL face. When a program is bombarded with so many exception possibilities due to when memory is low, there is no way it can possibly handle that and get out of the situation safely. It is just simply impossible. You are extremely extremely extremely naïve to believe otherwise. So once again do not blame the consequence of other stupid idiotic programming done by others upon us. You really really are demonstrating massive ignorance by thinking that Sierra Chart is both the operating system and all libraries and operates in complete isolation. This is just not the case. So not only are you seeing a stability problem within Sierra Chart due to faulty programming by others, but also the operating system, MFC and STL. And other libraries like parsers. To think all those others are perfect is completely ludicrous. They are all having problems. There simply is no safe way of recovery, once you run out of memory. Even if we did everything perfect in regards to catching exceptions everywhere, which is incredibly impossible, we would be working until we die, it does not change the fact that there is stability problems in all these other components including the operating system. Also your comments are exceedingly ludicrous, being that Sierra Chart is one of the most stable and reliable programs that runs on Windows. This is proven fact. We have tens of copies of Sierra Chart running our servers, for months at a time with complete stability. OK, after reading your entire post, we are going to openly call you "stupid". This is the dumbest commentary we have seen. You are not a knowledgeable programmer who understands the practical realities of programming. And how you cannot possibly be catching exceptions everywhere. This is completely insane and which makes the exception concept totally stupid which we have publicly said that many times. and if you have an expert level user base you should be listening to them not fighting them as they're basically doing free troubleshooting for you to make a better product for everyone You are not helping us in the slightest, and we are telling you to leave. You are not worth it as a customer.Also any symbol settings related items you have pointed out before generally is just wasting our time. 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: 2017-11-16 09:36:04
|