ScriptUO
Official ScriptUO EasyUO Scripts => Script Debug => Topic started by: Grandewd on May 06, 2014, 09:53:17 AM
-
** Note **. For any of you who frequent the Mainboard over at EasyUO, you'll note that I also posted this there - 5 mins ago. Hope you don't mind my also posting it here, but the brains here are IMO as good as anything over there... And that says a lot. Anyway, here's that post:
With all you excellent scripters here, some among you are also probably quite savvy tech-wise - and I'm hoping you can help me figure this one out.
I posted this over on Stratics/Tech forum last Friday, with zero response to date. I'm trying to figure out how this can be my system, and not UO/UOAssist.
When UO is loaded via UOAssist, my UO client balloons until it crashes. Memory leak comes to mind. This does not happen if UO client is loaded alone, and it does not happen to any other application that I have watched - only UOAssist.
I have already tried deleting all the user-config data that UOAssist keeps both in the doc folder and in the UOAssist folder, but that changed nothing....
Situation/data in the image:
(http://i1142.photobucket.com/albums/n616/grindy45/MemoryLeak_zpsb6d6bda3.png)
-
Did you notice if the memory kept climing up until the 15 minutes when it crashed?
-
I've noticed some Oddities with UoAssist as well. I'll take a look and let you know.
-
Looks like a Tool without Garbage Collector not finalizing their data. So it will just stack memory usage
-
Another reason to stop using UOAssist!
-
Did you notice if the memory kept climing up until the 15 minutes when it crashed?
If you mean does the memory usage constantly climb, then yes - it does.
-
Looks like a Tool without Garbage Collector not finalizing their data. So it will just stack memory usage
Um, say what?
-
Looks like a Tool without Garbage Collector not finalizing their data. So it will just stack memory usage
Um, say what?
Good code with proper garbage collection (memory allocation-deallocation) = GOOD
Bad code with uncontrolled garbage collection = BAD
It's easy to see good vs. bad just by monitoring memory usage over time of a program. There were times in UO executable days (especially the Enhanced Client) where you could see the memory run away until it crashed just because it hogged up your memory and cache.
-
Are you using Win7 or Win8.
I use Win7 and my Client.exe.32* with UOAssist running at 51,260K and CPU 02% after 2h45min. Few month ago I did had some problem with my laptop and hight CPU and had to system restore twice, Not sure why but it since to fix my problem :)
-
Yea, using Win 7... Hmm, ok - if you're running the current OSI client and UOAssist and you're not experiencing this, then it must be something with my system.
Gonna have to think on this a bit more... Thx
-
What are you running for virus software?
-
What are you running for virus software?
Running Norton's and am about to run a series of checks with several tools and see what they find...
-
I think you should test run with Virusscan disabled to see if it's contributing to your issue.
-
Good point 12... Norton's has not given me issues in the past, but I'll sure disable it and see... thx
-
Does memory climb at the username/password prompt?
Does it climb at the shard selection list?
Does it climb if you go sit in the woods with no creatures/players around and don't move?
Does it climb for a new, nude character doing nothing on an empty shard?
Does it climb if the UO account isn't registered to use UOA?
Does it climb if all the features in UOA are turned off?