DxNothing Causing Memory Leak?

[TheCerv]

Since the latest two of updates to Inner Space I've noticed that after about an hour of playing EVE with 5 clients active that the game becomes unplayable, either by causing strange anomalies with sound issues, or just straight up causes my whole computer to freeze. These issues hadn't happened previous to whatever updates were issued this week. After about 45 mintues to an hour my system becomes bogged down, the sound becomes distorted, my mouse cursor becomes sluggish and eventually everything becomes unresponsive, even other programs such as Mumble and Chrome. I can't even bring up my Task Manager.

After many freezes and restarts I began to slowly troubleshoot the problems. Finally when the system started to get bogged down, I found that closing the 3 DxNothing windows I've been using for the past week and a half (i'm new to ISBoxer) remedied this issue.

Perhaps there's some kind of memory leak with the latest versions? I have no idea, I'm not a programmer, all I know is closing the DxNothing's fixes the problem. Which this is a relatively simple work-around, it is a pain in the ass. It also doesn't work every time.


Anyone else having a problem like this?

[MiRai]

Perhaps there's some kind of memory leak with the latest versions? I have no idea, I'm not a programmer,

The Windows Task Manager will show you how much memory a program is using. Make note of how much memory the dxNothing windows are using when you first launch them, and then watch that number over time.

all I know is closing the DxNothing's fixes the problem.

Have you tried the reverse? Have you tried closing down Chrome, Mumble, or whatever else to see if they're causing the issue with dxNothing?

Do you have a lot of Video FX running? This has been known to cause issues in the past.
Are you using an Other Window Source with Video FX?
Are you repeatedly closing down viewers/sources and opening/creating new ones?
Is this a multi-monitor system? If so, are all monitors hooked up to the same GPU? SLI/Crossfire?
What OS are you using?

Also, if you believe this is directly related to an Inner Space update, then you can roll back to a previous version to test.

[TheCerv]

Indeed, I should have been watching task manager for that. I'll keep an eye out.

I have tried closing the rest of the non-essential programs to see if they were causing it. I originally thought it was mumble causing all the issues, but that turned out to be not the case. I know Chrome is a resource hog, but the issues happened whether or not I had it open.

Yes I am using a multi-monitor, Single GPU set-up. I'm not sure how many Video FX sources/views are a lot. I've seen some set-ups that have a ton of them, and some very minimal set-ups. I didn't think that I had very many in comparison, but perhaps that might be an issue as well.

I am using Windows 7 64bit.

I'll play around some more with Video FX stuff to see if I can reliably replicate the problem before rolling back to a previous version. Also here is a pastebin of my current ISBoxer settings if that might help. Maybe I've got something screwy going on there and changed a setting I shouldn't have while learning how to use it. http://pastebin.com/p0ppg5m8

[TheCerv]

So after some further investigation, it appears as though 2 of my 5 clients are the culprits. their memory usage starts at around 600MBs, but rises to over 750 each and after some time seems to cap out close to 850MBs while my other 3 clients stay in the 600-630 range. I feel it's worth mentioning that I've tested this is two methods, just sitting in station with all my characters, and performing the same mining activity in the same area. The result is the same for both. Closing and re-opening the clients starts the process all over again.

The fact that this only occurs on 2 of my 5 clients indicates that something is up with my ISBoxer settings, but all my performance settings are the same or similar. I'll try rolling back to a previous version of Inner Space and report my findings. Also for Reference my Current Inner Space version is 1.14 (build 6113)

[lax]

The fact that this only occurs on 2 of my 5 clients indicates that something is up with my ISBoxer settings, but all my performance settings are the same or similar

I'm not sure I follow the logic here. If something is up with your ISBoxer settings, wouldn't you expect it to either a) be something different between them in ISBoxer, or b) happening to all 5 clients?

Given that your ISBoxer settings are identical, but ISBoxer allows different client settings via Virtual Files, It seems to me that client settings might be a more obvious culprit. Did you check your in-game settings (e.g. video settings, etc) to see if something is different between the clients?

[TheCerv]

My video settings are Identical across all my game clients. In fact, 4 of my clients are cloned from 1 of the two causing problems. Strange that the clones aren't having the same issue...

Either way, I've rolled back to Inner Space build 6089. So far so good. Little sluggishness here and there but I would chaulk that up to only having 8gbs of ram. None of my clients have surpassed 655MBs of memory usage thus far where as before two would be well over 700 by now.



I wish I had thought of taking a screenshot like that when two of the clients were acting up.

[TheCerv]

Another Update:

So now I've been playing for nearly 3 hours. My Memory usage has gone up again, all clients are at about 800MBs, but I haven't had any of the really bad stuttering, audio distortion, or system freezes. All I've changed was the Inner Space version. So whether this is all an anomaly, or I've changed something else without realizing it, things are working good again.

For the time being, I'll stick with the older version of Inner Space.


P.S.
I do want to say that I love this software. So great job Lax, and I did end up buying a 3 month sub I will, however, wait until I can get some more RAM before adding any more additional clients to my fleet. Based off of the findings from this troubleshooting experience, I think I'm topped out at 5 with only 8GBs of Ram.