by TakisGen » Thu Jun 05, 2014 10:41 am
Hi Apprentice,
I think it is not practical to share a strategy file with 1300 lines of code together with a functions library of 1800 lines, not to mention the relating indicators that are at least modified versions of known ones. The strat file contains some hundred of parameters (it is "all in one") and only i could make it run, so i know it is of no use by someone else exept for educational purposes.
Instead, knowing that the problem is not in the actual logic of one of the strategies or in one of the indicators, i did some further search.
As i stated in my previous post all started trying to exclude passes with dd higher than a certain threshold from the results. Not being able to do that, i decided to flag those passes using the storagedb. Guess what, i was wrong in my previous post when i mentioned that this is another story.
Writting anything to the db causes lines like the following to appear in the log every now and then:
Critical error occurred. Optimization is stopped. 2014-06-05 17:59:10
Optimization pass 319 (10, 5, 7, 1) calculated 2014-06-05 17:59:10
...
Optimization pass 219 (10, 4, 6, 1) calculated 2014-06-05 17:56:32
Optimization pass 218 (9, 4, 6, 1) calculated 2014-06-05 17:56:30
Optimizer could not start strategy. Cause: (nil) 2014-06-05 17:56:28
Optimization pass 217 (7, 4, 6, 1) calculated 2014-06-05 17:56:28
Optimization pass 216 (6, 4, 6, 1) calculated 2014-06-05 17:56:27
...
Please notice that this is a session with 7000 passes never finishing.
You can reproduse the errors by writting anything in the db.
I did a quick test with both :put and pcall(:put) like:
DB.alfa:put("key1","data1")
local ret=pcall(DB.alfa:put("key1","data1 pcall"))
Both are failing now and then when using three of four cores but the same is not true when using one core.
I think that you will be able to reproduce this easily.
Can you please confirm this?
Now i have storagedb removed from the code and investigating if the EXCEPTION_ACCESS_VIOLATION crashes i have mentioned still exist or not. I am not sure if they are related to those errors in the log and dbstorage module. Any thoughts on this?
I will keep you informed about any findings from my side.
Regards
Takis