Amount of memory approaching the limit.

• 01/16/2018 at 4:11 PM #59660
  Nicolas

  Ok, so now, please send a console with a link referring to this topic and code reading authorization, I know someone at IT-Finance is currently trying to replicate the issue and he still has not been successful.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20828

  Been thanked: 4741 times
  01/16/2018 at 5:05 PM #59668
  Pierre

  GraHal wrote:

  … what is the launcher and what is Java mode?
  

  Hi GraHal,

  Basically, the ProRealTime Launcher is a program that downloads and launches the latest version of ProRealTime. It uses its own integrated and customized Java version (as a consequence, you do not need to install Java on your computer to use ProRealTime).

  When you click on the main link to start ProRealTime (image of the screen or button), the Launcher is used.

  The Java mode is only used if you click on the dedicated link (see image below). This mode requires the Java from java.com to be installed on your computer.

  Regards.

  Pierre

   

  

  Pierre

  Moderator

  ProRealTime

  Topics: 4

  Replies: 45

  Been thanked: 26 times
  01/16/2018 at 10:12 PM #59682
  Vonasi

  Nicolas wrote:

  Ok, so now, please send a console with a link referring to this topic and code reading authorization, I know someone at IT-Finance is currently trying to replicate the issue and he still has not been successful.

  Unfortunately now I cannot remember which exact code I was working on when the issue was at its worst and I also fear that I may have developed it to a state where it is nothing like the code at that time. I will search through my recent work and try to remind myself as I don’t have many 1 minute strategies. Unfortunately(!) my girlfriend is now back from a months visit to the UK and she now may have better use for my time than strategy research and time spent on this forum – so maybe expect a few less posts and a lot less library posts from me as we now have boat to get ready to go sailing in in spring and a list of boat jobs that is bigger than my list of market and strategy development jobs!

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  01/16/2018 at 11:18 PM #59684
  GraHal

  Hi Pierre

  Thank you, I am now happy it is the Launcher I use! 🙂

  I didn’t know the Launcher uses it’s  own integrated and customized Java version.  I always keep the Java on my PC up to date … thinking I needed to! 🙂

  I recall folk saying they open PRT with the .exe … alternative term for the Launcher?

  Cheers
  GraHal

  

  GraHal

  Participant

  Topics: 204

  Replies: 8399

  Been thanked: 2041 times
  12/05/2020 at 1:42 PM #152674
  PeterSt

  I know this is a (very) old topic, but I can confirm it is definitely the GRAPH function causing this. This concerns a so-called memory leak.

  https://www.prorealcode.com/topic/amount-of-memory-approaching-the-limit/#post-58934
  (verdi55 there talked about it already)

  Today (or at least the 6 months or so ago in V11.1) this problem is still there.

  What is harder to grasp for us guys, is that this relates to the amount of graphing itself. Thus indeed the more “lines” graphed, the more memory is consumed (and not freed). Also, lines (graphs) may be conditional (like a line showing that you have a position, vs not showing because no position).

  In PRT/IG only 5 graphs are allowed in parallel for a reason : their smaller server. So with IG you just can not use as much memory as you can in native PRT. Maybe someone notice the 10 times or so slower IG server services PRT than native PRT ? it just is so … (IG is incredibly slow in comparison).
  Confusing : Despite what I just said, notice that this graph data is done/maintained locally, BUT it is steered server side.

  Since V11 more Graphs are allowed in native PRT, just as that more historical data is allowed (at least with a Premium account this is so). But it is useless, because you can only use it a few times before the memory message kicks in again. Btw, closing down PRT and restarting it, helps. But it obviously does not help if you consume too much in the first place (like using too much historical data).

  Over time I learned to live with it by means of having groups of Graphs active and using them based on variables denoting those groups.
  If GraphGroup1Active then
  Graph Gain(…)
  Graph BrokerFee(…)
  Endif

  Using the commands sparsely will let me backtest for hours, but eventually the message will be there again and it will be time to restart PRT.

  Notice that once this message appeared a first time, your backtesting will run significantly slower (there’s a lack of memory indeed). If you continue (always crossing away the message), finally PRT will hang.

  Peter

  1 user thanked author for this post.

  GraHal

  

  PeterSt

  Participant

  Topics: 70

  Replies: 2287

  Been thanked: 695 times
  12/07/2020 at 8:52 AM #152803
  Nicolas

  You should provide examples of code used in order to replicate the issue you encounter about this memory leak. I’m sure the technical support will ask a system report about your computer configuration.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20828

  Been thanked: 4741 times
• Author
  Posts