Crash Reporter

[ddresser]

As I test RequestHistory, I am generating occasional crash reports. The dialog Crash Information 1.1 comes up, then the dialog Crash Reporter. The latter always gives me something like the following:

Received: 2220 1932 1242780 1242808
Generating crash report ...
Failed to save dump file to 'C:\DOCUME~1\Donald\LOCALS~1\Temp\sig48.tmp' (error 3100352)

Any idea how to correct this, and generate a dump file for you?

Thanks,
Don

[StarrM]

It's possible you may be attempting to process too many symbols. The Desktop API can only efficiently handle 50 to 100 symbols at a time, depending on your system resources.

[ddresser]

Starr, thanks for the reply.

My immediate concern is that I am not able to send you the crash reports that eSignal wants to generate. As indicated in the example I sent earlier, this always is because it is unable to save a dump file to the Temp directory. I would like to correct this.

As to the source of the crashes, I have determined that if I am quickly iterating a bunch of symbols, then about one time out of thousand, sending both eSignal.ReleaseSymbol(aSymbol) and eSignal.ReleaseHistory(aHandle) in close proximity generates a crash. As a workaround, the code now skips ReleaseHistory, calling it only when the program closes.

Don

[StarrM]

How many symbols are you looping through?

[ddresser]

After trading hours, I retrieve the current day's W, D, 60 and 5 price data for 3100 symbols. My program takes 30 minutes to run. The way the program works, up to ten symbols are allowed to be active at any one time, so symbols are being released frequently.

Since I stopped calling ReleaseHistory at the same time as ReleaseSymbol, the program has worked just fine.

I still would like to know why the Crash Reporter is not working.

Thanks,
Don

[AChan]

It looks like for some reason it can't write to your temp directory. This is usually an access issue, rather than an issue with the eSignal application. You might need to grant write access to the user.

[ddresser]

I thought of that, but access to the temp folder does not seem to be the problem:

1 I am running eSignal as user Donald on the Windows 2000 Pro OS. The dump file that eSignal tries to create is in C:\DOCUME~1\Donald\LOCALS~1\Temp\sig48.tmp,
in the example that I sent. The security properties for the sigXX.tmp files show that both Donald and Administrators have full control over the files. Lack of access to the Temp folder therefore does not appear to be the problem.

2 eSignal actually does create the indicated file in the Temp folder. The problem arises after the file is created -- the file size remains 0, and so there is no dump file to send to you.

What is error 3100352, mentioned by Crash Reporter?

I probably was required to install eSignal as Administrator. If so, I changed the security properties for the Program Files\eSignal folder and all contents to include Donald. Is this the source of the problem? Are there new files created by the eSignal app within eSignal folder which are needed for the creating the dump file, and which might not be accessible by Donald?

Thanks,
Don

[StarrM]

Yes, eSignal should be installed and operated under an administrator account. This may be part of the problem.

[ddresser]

There is no way that I am going to run eSignal as Administrator. If that is a requirement, I must say that I am disappointed that eSignal thought requiring that the users do so was a good idea.

Someone there should think about computer security issues.

Thanks,
Don