Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Tue, 07 May 2024 23:26:13 +0000
non.NET - out of memory, out of bounds, data loss in a spreadsheet
View Count: 2257
| [2013-10-01 16:42:15] |
| namlem - Posts: 94 |
|
Hello SC team, i'm trying to port my formulas from .NET platform to non.NET. I have created Study Spreadsheet system Alert from scratch and copied most of formulas step by step using new reference addresses. I have several charts, one of them refers other. Soon after as I sat Number of rows to 50k and executed study i got an error: Exception caught from study function: angles4 | 2013-10-01 16:15:28 application still tried to process the study, but i could navigate through the software (it hasn't stuck) then I called Study menu and got other error : An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 7, wParam: 721770, lParam: 0 | 2013-10-01 16:16:30 later other error appeared in the log: Base Graph DateTime: Out of bounds array error at Index: 52120 | 2013-10-01 16:19:13 afterwards dialog box popped out saying "Out of memory", even though i have 16GB RAM in my PC and 8GB was in use. At this moment this SC instance used ~3.9GB of RAM. but the worst thing, that i had to close application and after restart all my formulas in columns O-AA have gone! Yes, im sure i saved it several times. I also restarted software few times before. --- ok, error "Out of bounds array error at Index: 52120" - probably due to the fact that the chart with study had more columns than the one it referred. "out of memmory" might be related to 4GB limit per instance i guess. but data loss after restart is completely unacceptable! under any circumstances! please see below for a log file: File >> Disconnect selected. | 2013-10-01 16:15:06 SC Forex Data (FXCM): Disconnected from the market data server. | 2013-10-01 16:15:06 Exception caught from study function: angles4 | 2013-10-01 16:15:28 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 7, wParam: 721770, lParam: 0 | 2013-10-01 16:16:30 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 7, wParam: 721770, lParam: 0 | 2013-10-01 16:16:53 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 7, wParam: 721770, lParam: 0 | 2013-10-01 16:16:54 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 87 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 196738 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 327857 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 524510 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 655625 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 852273 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 852313 | 2013-10-01 16:16:55 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 983422 | 2013-10-01 16:16:55 An unhandled exception was caught in c_Chart::WindowProc. Message: 32769, wParam: 32804, lParam: 9306680 | 2013-10-01 16:16:59 Warning: Caught an exception during the processing of a timer event. | 2013-10-01 16:17:25 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 513, wParam: 1, lParam: 9371759 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 1, lParam: 9371759 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9371756 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9371754 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9371751 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9371749 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9371746 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9371744 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9502813 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9502811 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9502808 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9699411 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9699406 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9830473 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 9830466 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 10027066 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 10027056 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 10027046 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 10027031 | 2013-10-01 16:17:33 An unhandled exception was caught in c_MDIDetachableWindow::WindowProc. Message: 512, wParam: 0, lParam: 10027016 | 2013-10-01 16:17:33 An unhandled exception was caught in c_Chart::WindowProc. Message: 32769, wParam: 32804, lParam: 7209543 | 2013-10-01 16:17:35 An unhandled exception was caught in c_Chart::WindowProc. Message: 32769, wParam: 32804, lParam: 9831003 | 2013-10-01 16:19:11 Base Graph DateTime: Out of bounds array error at Index: 52120 | 2013-10-01 16:19:13 |
| [2013-10-01 22:46:10] |
| |
|
Thank you for these details. We will work on this problem. Keep in mind, that the new non-CLR spreadsheets are still considered a beta at this time. Are you referring to saving the spreadsheet file itself?: but the worst thing, that i had to close application and after restart all my formulas in columns O-AA have gone! Yes, im sure i saved it several times. I also restarted software few times before.
Was the spreadsheet active and then did you select File >> Save or did you do File >> Save All. Send us the spreadsheet file that you saved. Attach it here. 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 |
| [2013-10-02 07:23:48] |
| namlem - Posts: 94 |
|
I don't save spreadsheets files one by one and almost never use File--Save, I always use File--Save All and later backup full folder. Was the spreadsheet active ?
sorry can't tell you, i guess it was visible, but focus what on a chart.I can't attach spreadsheet since its size is 146MB. Interesting to notice, that in .NET (edited) version the same spreadsheet was about 12MB. what i can do, is to reduce number of rows and then attach it, but no formulas inside since they have gone. Let me know if you still need it. Date Time Of Last Edit: 2013-10-02 10:23:17
|
| [2013-10-02 08:51:06] |
| |
|
We are not sure what the issue was with the formulas not being saved. We need steps to duplicate the problem. We have duplicated the array bounds violation error and maybe that is related to it. So we will solve that first and then see if there still is a problem.
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 |
| [2013-10-02 12:37:46] |
| namlem - Posts: 94 |
|
FYI today I also noticed that after that crash, General Settings 'Scroll Multiplier' value and changed width of columns in Spreadsheet have reset to default. |
| [2013-10-02 16:45:03] |
| |
|
This may have been caused by a memory corruption due to the problem. The issue will be resolved.
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 |
| [2013-10-02 18:29:17] |
| namlem - Posts: 94 |
|
Another weird behavior may be related to the issue above when formulas disappeared... Opened same spreadsheet for alert, added study 'Three lines break chart' and then removed it.. as a result somehow all Studies' values moved to the left, headers overwrote headers in columns A,B,C,D and values got overwritten starting column E... can't explain better. please see a screenshot and video screen recording. |
Private File Private File |
| [2013-10-02 21:46:39] |
| |
|
We will look into this.
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 |
| [2013-10-03 07:07:39] |
| TastyRisk - Posts: 119 |
|
after restart all my formulas in columns O-AA have gone! Yes, im sure i saved it several times. I also restarted software few times before.
I suffer similar after SC has crashed. I believe it's because some buffers are only flushed to disk after a clean shut-down. |
| [2013-10-03 07:12:54] |
| |
|
I believe it's because some buffers are only flushed to disk after a clean shut-down. We will check on this. In general, this would not be a problem with the vast majority of functionality that Sierra Chart has since the file I/O uses the OS functions directly. However, the spreadsheets are partially based upon a new development framework called QT. We will have to look into this possibility. 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 |
| [2013-10-03 07:16:16] |
| |
|
We have just now verified that spreadsheets are written using the Windows OS functions. So even with an abnormal shutdown of Sierra Chart, all data will have been committed into the operating system buffers. Therefore, your conclusion is not going to be valid at least when it comes To internal memory of Sierra Chart. Whether Windows has a problem committing data written to a file to disk when a program abnormally shuts down, we do not know. Our general belief is that it does not.
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 |
| [2013-10-03 08:51:40] |
| namlem - Posts: 94 |
|
I dare to assume, that formulas loss might be due to a new dynamic representation/address of Studies. I reproduced the problem where studies' output shifted to the left, by overwriting formulas columns. Maybe in TastyRisk's case it also took place, but was not possible to notice. |
| [2013-10-03 22:13:29] |
| TastyRisk - Posts: 119 |
|
What I see is this (unrelated to spreadsheets); If I specify a set of Files to load on start-up, and then have a crash, it has not remembered my choices. Sorry if this is *totally* unrelated to the OP issue. |
| [2013-10-03 22:44:48] |
| |
|
If I specify a set of Files to load on start-up, and then have a crash, it has not remembered my choices. 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: 2013-10-03 22:45:30
|
To post a message in this thread, you need to log in with your Sierra Chart account: