This is in regard to the crashing behavior have noted which seems to occur much more on Monday mornings than other times.
This morning for the first hour eSignal was crashing on me about once every one to two minutes, between 6:30 and 7:30ish (PST). Now for the past half hour, from 7:30 to 8:10 it hasn't crashed at all. But first hour probably 40 total crashes. Makes it a bit hard to watch the market, eh??
I ran my sample test app which submitted to Robi, and actually it didn't cause crashing any faster than normal. It doesn't do DDE quotes, which might be the difference.
The error is similiar to the one that kept getting in the pre-7.7 releases, but what looks to be the null pointer offset is 0x14 rather than the previous 0x28.
The text of the message is:
"The instruction at "0x5ad71531" referenced memory at "0x00000014". The memory could not be "read".
The attached BMP shows one of the crash dialogs, coming in "DBC Tick Message Sink". The location where it tags this can vary.
Would be great to see this resolved!
-Jim
Woops - spoke too soon. 8:14 and crashed again. The crash does happen intermittently outside of the Monday window, probably ten to twenty times during the day, but whatever is happening on Monday morning, probably server side generated data, is what pushes it much more than other times. Can run fine for an hour then get a crash, when not actually doing anything programmatically.... Hope this helps find this!
This morning for the first hour eSignal was crashing on me about once every one to two minutes, between 6:30 and 7:30ish (PST). Now for the past half hour, from 7:30 to 8:10 it hasn't crashed at all. But first hour probably 40 total crashes. Makes it a bit hard to watch the market, eh??
I ran my sample test app which submitted to Robi, and actually it didn't cause crashing any faster than normal. It doesn't do DDE quotes, which might be the difference.
The error is similiar to the one that kept getting in the pre-7.7 releases, but what looks to be the null pointer offset is 0x14 rather than the previous 0x28.
The text of the message is:
"The instruction at "0x5ad71531" referenced memory at "0x00000014". The memory could not be "read".
The attached BMP shows one of the crash dialogs, coming in "DBC Tick Message Sink". The location where it tags this can vary.
Would be great to see this resolved!
-Jim
Woops - spoke too soon. 8:14 and crashed again. The crash does happen intermittently outside of the Monday window, probably ten to twenty times during the day, but whatever is happening on Monday morning, probably server side generated data, is what pushes it much more than other times. Can run fine for an hour then get a crash, when not actually doing anything programmatically.... Hope this helps find this!
Comment