Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
How to resolve this problem? - ERROR: Failed to call 'Add' method for period type 'Tick': Exception of type 'System.OutOfMemoryException' was thrown. I am using 6.5
Much appreciated. Thank you
Can you help answer these questions from other members on NexusFi?
First have a look at the trace file. It should tell you something about the offensive indicator or strategy.
If you look for an answer from us, we would need more information. Which datafeed do you use? Which indicator or strategy caused the problem? What was the lookback period of your tick chart? Which was the instrument? How many other indicators were on your chart? How much RAM has your PC?
Thanks Fat Tails. I should have provided more information to start with. I was not having this issue ever it is only since past month that I have this issue. I was trying the elimination route to isolate the issue since I thought something else on my laptop could be causing this. I tested by using a naked chart with 15 day period look up using 4 Renko (previously I used to have 4 similar charts with 5-6 indicators on each). I suspect ever since I upgraded to the latest service pack that I have been having this issue. There is no issue with RAM or any other factor. I checked the trace file and could not get any material information over the issue.
forgive me if this is not remotely the problem -- but i have had similiar error when
programming and the code is run and it has hit a division by zero which it cannot cope
with.... are you running a strategy/indicator that you need to debug?