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)
Looks like it's gaining some momentum - It may be worth considering a thread of its own for this one - to ensure a more proper title may catch all the people that may be interested/affected by this. The current "NT8 not ready for prime time" may put some NT aficionados off.
You may be right. I think it's hard to say, and I am surprised at the level of response so far.
My thought in using this thread was just that it's a kind of a catch-all topic for NT8 issues. I think this issue may be of limited concern to most users, and I posted the last update just to see if it still has any juice left.
And of course, while I would like this to get fixed, it's not like they have nothing else on their plate, issues that affect more people or are more critical.
I'm actually thinking that the 8 or so votes we got (including mine from my post) is not that bad, and they are added to whatever votes the topic originally had -- remember, it was an already-existing request. It should stand out somewhat from run-of-the-mill, random suggestions, anyway.
My thought is to see what interest there may still be, but not to make a crusade out of it.
I think this has been a great thread. It is a One-Stop thread to see other peoples issues and to post or find help. If we break it up, then we may not have as much interaction..... Personally, I have taken other peoples thoughts and melded with my thoughts to come up with some fixes to some issues and then posted for others to look at.
Hi ScottieMickey...I trade on NT 8 and have for the past 18 or so months. It took me about 3 months to find a way to make it stable and for memory to not run rampant. I wrote a batch file to cleandata directories prior to start.
As for the indicators, I write q fe of my own. C# does take some getting used to. My code is simple, and it takes me awhile to plow through. Ninja allows you to run both at the same time. I would suggest that before startup, you delete both cache directories, and the 3 data directories (min, day and tick). The bat that I use every day is posted in here somewhere...
I never had such a problem.....until last night. Even with nothing open in a workspace it's using 2100 mb of ram FFS! This must be the data caches. I didn't have an issue until I started using the new version of rancho....
I have had a few issues, but I never have had these memory "running rampant" issues.
This suggests to me a "memory leak" -- some code, in an indicator or strategy, that is using and not releasing memory when it should, so the amount of memory used balloons and the amount remaining available for the program becomes less and less (that's why it's called a "leak") until it crashes. This is classic memory leak behavior, and is generally due to incorrectly written code. In NT8, not disposing of custom brushes has been an often-cited culprit. There may be other sources of the leak as well, but it is apparently not in the basic platform, but in added code. (I'm not saying the platform is perfect, nor that it doesn't still have issues, but a memory leak is apparently not one of them, at least in its current version.)
I do not think that you will experience this problem with bare NT8, using no indicators other than what came with the platform. Then if you add in anything, one at a time, that you have either written yourself or acquired from any other source, commercial or otherwise, at some point you will probably find the source of the problem. Make sure you have the current version installed, of course.
Do you have the memory issues with nothing at all but a bare chart running, including nothing in any other open workspaces? If you don't, that would be your starting point. If you still do, I would save everything to other folders and then do a complete uninstall, then also delete the NT folders, which the uninstall will leave behind (both in Program Files (x86) and in Documents), and reinstall from scratch. You need to know you have a clean starting point.
I confess that I do not have any idea why deleting directories would matter, but (a) I have never needed to do that, and (b) it still sounds like you have a memory leak, whether you have something else or not. I know that many users do not have these problems, so cutting back to a bare, clean install, and then working forward, gradually introducing new code, will likely find what is causing it.
Obviously, if you try this approach you will probably find it tedious, and you will definitely want to save everything to a separate folder before tinkering with anything.
But I don't think that the experience of the user community at this point supports the idea that you need to take extraordinary measures to have a system that does not eat up memory until it crashes. Something else is going on, and probably it's in your user-created or third-party-created code. This is a bummer, since it means that something you really like and use is likely the problem, but there it is.
Good luck, and I do mean this. These leaks are a pain to track down. You may prefer the band-aid of running the batch file and living with it, but that may mean you have an uncorrected problem that may bite you later.
Hi Bob, I have not had the memory issues in well over a year now. Between the revs of the basic platform and my directroy clean before start, I am running very stable. You are correct about the rogue indies.
I find it interesting though , that cleaning the old data before startup was The Key for me. I dont know if I still need to run my bat file at startup, but it clean directories and starts NT8 in high priority, so why not... I have to start with a click either way. I am quite happy with NT 8.
P.S. Another key to stability is to not mess with charts all the time. Changing indies seems to trigger memory builds and corrupt workspaces.
You definitely could be right that needing to run that batch file was necessary earlier on. The history of NT8, and its various issues, has been a strange one.....
Glad you're no longer having the memory leaks. I know there still are NT8 issues, just not as much as it used to have.
I do think that anyone who is finding memory running amok should look to any new indicators or changes to indicators, and see if taking them out fixes the problem. Odds are good that it will....