[116] SQX stops if 85% of memory are used, even though I´ve disabled that protection
On build 116 SQX seems to stop if 85% of memory are used, regardless if that protection is disabled in the options. I understand that high memory usage can cause troubles and you can enable the 85% memory protection by default on new installations, but I think for experienced users this protection should not be forced all the time and should be able to be turned off, because it leaves to much memory unused. For example, on 128 GB of RAM, using just 85% of it would mean that 20 GB can never be used (as 85% of 128 = 108 GB) and that´s not cool at all :-)
Thanks :-)
Attachments
No attachments
-
Votes +3
-
Project StrategyQuant X
-
Type Bug
-
Status Fixed
-
Priority Normal
History
g
g
Rr
NF
TB
Tomas Brynda
04.01.2019 09:12
When did you experience this problem? If the option for memory protection is disabled, projects should be running no matter how much memory is used. A project should stop only if OutOfMemoryError occurs.
There is a memory protection when initial strategies loading is processed on a program start though. It cannot be disabled. In past we have run into situation when there was huge amount of strategies inside projects and SQ crashed when it was trying to load them all. But if you have so much RAM available, then it is almost unreal to allocate so much memory on startup :)
I tried switching the memory protection option on an off and check that the change was saved accordingly and it works fine. But restart of SQ is needed when you do such changes.
g
geektrader
04.01.2019 09:33
This happens each time during genetic generating when heap memory reaches 85% of it´s fully allowed limit. I´ve switched this protection off, and of course, restarted several times already. I still get it once 85% is reached and it stops SQX, just like if that option would be enabled. Did not happen with 115 and makes no sense to me. Has any of the up-voters experienced it? Some replies would surely be helpful for Tomas.
MF
Mark Fric
04.01.2019 12:52Status changed from New to Fixed
I believe the problem was caused by the memory leak in 116, there was an OutOfMemory exception being thrown. It should be fixed now.
Mark.
Votes: +3
© Copyright. All rights reserved. ProjectPanel.com
