Home >> Support Board

Support Board

Date/Time: Tue, 07 May 2024 15:55:53 +0000

How to Post a Message for Support

Post From: Warning: Caught an exception during the processing of a timer event

[2017-07-13 19:05:06] Link To Thread - Link To Post [Go To First Post]
i960 - Posts: 360
This doesn't seem to be 100% related to custom studies. I also get these errors on trying to load up all my chartbooks on a fresh restart (probably 40 chartbooks total). I've seen it through various versions over the last 6 months or so. I'm currently running a pretty recent version as well (updated as of last week). Here's what I see in the logs: CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201612-NYMEX to CL-201701-NYMEX occurs at 2016-11-17 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201701-NYMEX to CL-201702-NYMEX occurs at 2016-12-16 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201702-NYMEX to CL-201703-NYMEX occurs at 2017-01-18 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201703-NYMEX to CL-201704-NYMEX occurs at 2017-02-16 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201704-NYMEX to CL-201705-NYMEX occurs at 2017-03-17 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201705-NYMEX to CL-201706-NYMEX occurs at 2017-04-18 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201706-NYMEX to CL-201707-NYMEX occurs at 2017-05-18 \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 121393 Volume #9 \| Volume based rollover from CL-201707-NYMEX to CL-201708-NYMEX occurs at 2017-06-16 \| 2017-07-13 11:23:12 HD Request # 1305 \| Receiving historical Daily data for CLF99 starting at 1996-08-21 \| 2017-07-13 11:23:12 HD Request # 1305 \| Writing historical Daily data to the file CLF99.dly \| 2017-07-13 11:23:12 HD Request # 1305 \| Received 566 records from 1996-08-21 00:00:00 to 1998-12-21 00:00:00 (2.3 years) and wrote 566 records for CLF99 \| 2017-07-13 11:23:12 HD Request # 1305 \| Daily download COMPLETE for CLF99. Completion time: 2s. Unique request ID: 2953 \| 2017-07-13 11:23:12 Removed historical data download ID 2953 \| 2017-07-13 11:23:12 Error reserving space for Time and Sales for symbol. \| 2017-07-13 11:23:12 * HD Request # 1306 \| Downloading Historical Daily chart data for CLZ98. Starting date: 1967-07-14. Service: ib \| 2017-07-13 11:23:12 HD Request # 1306 \| Using user Barchart Historical data account. \| 2017-07-13 11:23:12 HD Request # 1306 \| Requesting historical Daily data for CLZ98 starting at 1967-07-13 \| 2017-07-13 11:23:12 Warning: Caught an exception during the processing of a timer event. \| 2017-07-13 11:23:12 * Warning: Caught an exception during the processing of a timer event. \| 2017-07-13 11:23:12 * Warning: Caught an exception during the processing of a timer event. \| 2017-07-13 11:23:12 * HD Request # 1306 \| Receiving historical Daily data for CLZ98 starting at 1995-05-04 \| 2017-07-13 11:23:12 HD Request # 1306 \| Writing historical Daily data to the file CLZ98.dly \| 2017-07-13 11:23:12 Warning: Caught an exception during the processing of a timer event. \| 2017-07-13 11:23:12 * Warning: Caught an exception during the processing of a timer event. \| 2017-07-13 11:23:12 * CL-201708-NYMEX [CV] 46368 Volume #3 \| Reloading chart. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201607-NYMEX to next contract occurs at 2016-06-17. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201608-NYMEX to next contract occurs at 2016-07-18. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201609-NYMEX to next contract occurs at 2016-08-18. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201610-NYMEX to next contract occurs at 2016-09-16. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201611-NYMEX to next contract occurs at 2016-10-18. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201612-NYMEX to next contract occurs at 2016-11-18. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201701-NYMEX to next contract occurs at 2016-12-16. \| 2017-07-13 11:23:12 CL-201708-NYMEX [CV] 46368 Volume #3 \| Date rule based rollover from CL-201702-NYMEX to next contract occurs at 2017-01-18. \| 2017-07-13 11:23:12 After that the situation becomes very bad. If I close everything out, various chartbooks will be written out with 18 bytes of data containing only: 00000000 53 43 5f 43 48 41 52 54 5f 42 4f 4f 4b 00 be 00 \|SC_CHART_BOOK...\| 00000010 00 00 \|..\| It even does this if I say "no" to "save all?" The other problem is that it's hard to determine where this error is actually occurring because so much stuff is going on in parallel. Based on my own history of threaded programming it has the feeling of a thread race (multiple things accessing the same data without a lock) somewhere. It would also help if that error message were associated to a particular chart or chartbook so we have some kind of clue which one is associated with the exception.