Version 7.2 Errors

[ACM]

David

As an aside notice that in the image I posted earlier I actually have the Time Template set to load a specific number of days when the interval is Daily.
In the second line of the 24 hour Time Template there is D for Daily and 300 bars as the maximum request.

I would like to take this opportunity to suggest to Matt to implement - if possible - also a way to modify the number of loaded bars 'on the fly' by using the method available in the Get standalone package.
There it is done by typing [ (ie square bracket) followed by the number of desired bars.

Alex

[mbuta]

Hi Andy and all,
Obviously, the subject is of interest to quite a few others.
The problem exists, systems crash quite often.

Don't scroll back, wait for "enough" data, don't do this, don't do that, are all proofs that there are problems and maybe someone should look into them.

My observation (and belief) is that eSginal "accumulates" data and does not refresh its data bases properly and discard gracefully old data from stacks.
Therefor, the more data one uses (more bars, more indicators, more charts, more symbols, etc.) it is only matter of time before the program crashes. After it crashes once, it keeps crashing, regardless of what we do (including "reset data bases" in Data Manager, or "Reset Symbols" in File menu).
During normal trading hours, when I switch between symbols and time intervals quite often, I have to reboot my computer at least least 2-3 times. Not very pleasant when you have open positions for short trades.

Even today (Sunday) it started crashing on the same layout I always do my drafting on (two Adv charts and one quote window). It worked fine all Saturday, but I forgot the computer and eSignal open over night.

Thank you.


To avoid crashes, this works: 1) Don't open tick charts until there's enough data to fill the chart (e.g. For US equities, don't open tick charts until about 9:00 AM ET, an hour after 8:00 AM start of data), 2) Don't scroll any charts backwards beyond the point that there is data; 3) when the program is loading data for any reason (opening a chart, application of a study to a chart, etc.), don't do anything in eSignal until it's finished, and 4) don't use playback.

quote:
Originally posted by AndyS
Hi Mihai,

While we have heard of very few incidents of sporadic crashes, by and large there have been no reports of this on a broad basis. We now have thousands of users on 7.2 with no complaints, so when you ask if anyone is working on the problem, we don't see the problem. This is not to say you don't have a problem, but we are led to believe it's isolated to your system. . . .

Regards,
Andy S.
eSignal Support

[atlas]

I have nothing constructive to add except to say that eSignal has been running quite well as of late. I run several charts with one or two indicators, a tick chart, and some editor windows. It is true that 7.1 and some of the early 7.2 betas were prone to crashing, particularly when loading the max intraday history or scrolling back several days in a tick chart, but I have not encountered these problems at all with recent builds and in fact have not seen eSignal crash even once in weeks.

-CB

[mbuta]

Thanks,

This means I am doing something wrong which Tech Support of eSignalwas not able to spot. We spent hours together, they entered my computer directly, etc.
All I can say is that is has been and continues to be very frustating.

"I have nothing constructive to add except to say that eSignal has been running quite well as of late ... "

[AndyS]

Hi Mahia, Lancer,

Mahia, I don't think you're doing anything wrong, but it might have to do with what else you're running or what custom formulas you may have or a combination of different things. That's why I asked for a complete copy of your layout so that we could do testing with the same files as you.

Lancer, I did do two sets of test last week (Mon. & Tue.) using the steps you have previously outlined. I could not reproduce. On Monday, I left my home computer on through out the night, then just after 5am pst, I ran the steps you have outlined without a problem. On Tuesday morning, I turned on the pc prior to 5am pst and then ran the steps just after 5am. Still no problems.

At this point we are not hearing back through the phone banks or on our Tech emails of a wide spread problem of 7.2 crashing. Again, this does not mean there's no problem, but that it's isolated to conditions we haven't discovered yet that effect only a few. This will make it tough to find & correct. For this reason, for us to help you out, please post your layout & data files to my File Share site - Andys Group. The link is here. I don't think it'll help to email me your settings, rather I'd like to test the files w/any custom formulas you may be using.

You help in determining this problem is greatly appreciated.

Regards,
Andy
eSignal Support

[mbuta]

Re: Reply to post 'Version 7.2 Errors'

Hi Andy and thank you for encouragement, but I am convinced I am doing
something wrong in my custom indicators, which is when I get most crashes.
Some errors I already spotted and corrected, like I was checking for null on
some variables.
Others are not so obvious and, although I am a powerful hardware architect,
I am a poor software designer, I know that.
My gut feeling tells me that there still some special situations
(exceptions, like you guys call them) that might not be treated by efs
environment. When they happen, and guarranteed there will be dummies like me
to generate them, the crash is normal.

Other environments provide for such situations and allow you to process
exceptions.
...
OnError (blah blah blah)
return label

I did not see anything like that in efs. This might be the first step in
helping us with a solution.
An other step would be to provide us with guidelines of things that can
create exeptions and how to avoid them.

If you want to crash your system I recommend the following setup:
Make a custome indicator that calls 15 or so studies (Ma, Oscilators, MACD,
ADX, Stochastics).
Run that on two charts that are linked to a quote window (15-20 symbols) and
play with symbols and intervals (1-5-15-30-60 minutes) during normal trading
hours.

Thanks again.





----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Monday, February 17, 2003 10:19 AM
Subject: Reply to post 'Version 7.2 Errors'


> Hello mbuta,
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>

[mattgundersen]

Just want to re-iterate what Andy is saying - we haven't been able to reproduce this. If you could send us your ACH and any associated EFS's, we will be more than happy to put this on a test machine, reproduce, and fix.

m.

[AndyS]

Hi All,

I was just talking with one of our senior Tech Reps who was working with a client that was experiencing similar problems described in this thread. Our rep did, what we call, a webex session in which the rep was able to see the client's computer, what they had installed on it, and what they were running at the time that eSignal would crash. Turns out our rep identified certain software applications that appeared to be causing the problem. With the approval of the client she was working with, she removed the software and the client hasn't experienced another crash.

I know what you're thinking, "I don't want anyone deleting the software that I have"! That may not be necessary. What I want to do is, if you're still experiencing this problem and still want help (and apparently don't want to send me your layouts / EFS custom formulas as I haven't received any), please private mail me and I can set up an "appointment" with this rep to do a webex session with you to try and determine the problem.

Looking forward to hearing from you all on this issue.

Regards,
Andy
eSignal Support

[mbuta]

Re: Reply to post 'Version 7.2 Errors'

Hi Andy,
Thank you for continuing to try to solve my problem.
First, I do want to send you my layout, but I do not know how and I have
asked for instructions.
Second, a rep from eSignal already had a Webex session on my computer, but
was unable to sopt anything (I do not run any other software in the same
time with eSignal, I have a second computer at my desk).

I do believe that the problem is in my custom indicators. I am not a power
Java programmer and the available documentation is so limitted.

I further believe that, if EFS environment would provide a gracefull
treatment of exceptions, many of the our existing problem would dissapear.
Failure to check for "null" variables/inputs is the most common problem. We
all generate nulls in the first bars of study until enough bars are
available.
The bar counter in efs is backwards, which makes it dificult to use it.
I know, you will say that can be done and I agree with you, but this is my
point: anything can be done if ....., but we TRADERS not PROGRAMMERS and I
have no intention to look for a job as programmer soon.

Thank you,
Mihai Buta

----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Monday, February 24, 2003 3:55 PM
Subject: Reply to post 'Version 7.2 Errors'


> Hello mbuta,
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>