Spring RTS Engine

Somebody has a idea why it uses sometimes such a lot of performance? And 1,5 Ghz should be enough for the Springdownloader or not .

How long did it use the cpu for? I needs brief bursts when processing your maps and mods; more would be a bug.

And either attach your image to your post or use a hosting site that doesn't pop up ads that can be unremovable depending on browser size.

It used the CPU as long with ~100% as I stopped it after a few minutes.
And what do you want to know with your second question?

PS: when I try watch my pic,there is no pop-up!?

schmidt100 wrote:PS: when I try watch my pic,there is no pop-up!?

Well it hates me.

now it should work!

EDIT: what do I have to do to show the pic?

It is using over a GB of ram too

Yes that was also strange, because it filled up the RAM until ca. 1000MB and then it startet with circa 500MB and countet up to ~1000MB again... the hole time

whoa?? 1000mb??
makes no sense..
perhaps its some map/mod you have?

no idea..

It was the first time that this bug appeared and you can see what I downloded (Spring:1944 v0.92) and uploded (one map).

I've several times had spring DLer fill the windows temp directory, all 100 some odd gigs of HDD space filled with assorted temp files.

Almost definitely unrelated... I just like making fun of spring downloader.

Yes, what happened to SpringDownloader? From a small, lightweight program it has became this huge bloatware...

I'm not saying I don't appreciate the new functions, but isn't there a way to make it so heavy? Look at muTorrent fo instance...

WHAT IS THIS FAGGORTY!!??

Well something was causing the widget module to leak massive amounts on each refresh, not sure if that got fixed yet.

I now switch it off asap, because when it's running I get timekicked from half of the games.

lurker wrote:Well something was causing the widget module to leak massive amounts on each refresh, not sure if that got fixed yet.

This was in the previous version when the widget module used a bugged LuaInterface-DLL. The current version does not use the DLL at all and does AFAIK and hopefully not leak memory. Maybe the next version will use it again but the leak should be fixed in the updated DLL.

Could someone tell who had SpringDownloader at 1GB for how long it was running when that happened?
Maybe you could try to disable one module after another until it does not happen anymore. Figuring out which module does cause it would help alot to find the problem. Thanks.