Moosetek13 wrote:QUOTE (Moosetek13 @ May 23 2007, 02:28 PM) Watching Task Manager, as I start ASGS it consumes 18,768kb of memory.
When I log in and it attempts to start Allegiance it goes up to 26,448kb.
And now, just sitting idle and logged off, it will periodically increase its mem usage.
It is now up to 26,844kb. It has increased its memory usage by nearly 400kb just sitting idle for 5 or 6 minutes.
In fact, it seems that whenever it gets focus it takes another 8kb or so of ram.
It is now up to 26,872.
26,880
26,892
26,896
26,904
26,912
Edit:
42 minutes later, it is at 27,224kb
Is this normal?
Yeah. It's on the high side of normal, but it's normal.
Insert very generalized observation: Part of this is due to things not optimizing by default in the libraries. It'll just continue to use more and more by not clearing things out of 100% of the unused memory addresses until a flush is called. Most windows-based apps do this, especially older or smaller ones because there's either little reason to optimize (optimization takes a ridiculous amount of time and usually breaks more than it fixes) or it's designed to scale specifically to the maximum of what your machine can take (i.e. it grows until it's not allowed to anymore).
Aside from ASGS doing a bit of this, Allegiance does it far moreso. (It's older code, and worked on by a team of developers instead of a single one.). Allegiance is very good at finding weaknesses in your hardware for that reason.
Moosetek13 wrote:QUOTE (Moosetek13 @ May 29 2007, 05:11 AM) Am I rude, lude, and socially unacceptable? What???!!!
Nope. You just managed to catch us at a time where people were incredibly busy with RL. I'm still filing 5-page expense reports from mid-may and I'm due to fly out again in a week and a half. Sorry I didn't get to you sooner.
People about Antivirus wrote:...
BitDefender is usually pretty good compared to things like Norton or McAfee. It's been a good year since I've worked with it, but it never seemed to have the usual bloatware and internal-blocking that comes standard with other packages. It's kinda like AVG only better.
ImmortalZ wrote:QUOTE (ImmortalZ @ Jun 1 2007, 12:07 PM) Try unchecking the Launch Allegiance option in ASGS and then launching Allegiance manually.
Or try rightclicking the Allegiance Executable and running it in Compatibility mode, just for the hell of it.
It shouldn't make any difference and might break worse, but depending on what turns up, it could be more data to work from.
me wrote:New Question....
Can you ping and tracert
69.93.201.146
Paste your results here.
Do the same with:
69.93.201.149
That ought to be a good start.