SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001891SphereServerexecutable - windows buildpublic17-01-11 12:3124-01-11 15:27
ReporterTerrikate 
Assigned ToMrSugarCube 
PrioritynormalSeverityblockReproducibilityhave not tried
StatusclosedResolutionduplicate 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Nightly VersionAutomated (specify build number)
Experimental FlagsDiagonalWalkCheck, New_Triggers, Script_Profiler, Size_Optimise, UseNetworkMulti
Option FlagsCommand_Sysmsgs, FileCommands, Buffs
Internal Build Number1395
Summary0001891: Compress failed with error -4 when generating gump. Using old packet.
DescriptionYesterday I switched to the latest version of the emulator (I was using 3 January, I was wrong) and I found the error in the description in less than 24 hours on two occasions.

In the first case with UseExtraBuffer enabled server still worked but people could not connect, no saves were made.

The second error after 3 minutes the server crashed.

Sphere reports (crash dumps) are all 0KB.

All players are using UO: 2D Client SA 07082
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0001868resolved MrSugarCube Sphere has a major memory leak 
Attached Fileszip logs.zip (258,824) 17-01-11 12:31
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=51&type=bug
jpg sphere_block_again.jpg (431,716) 17-01-11 22:05
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=52&type=bug
Issue History
Date ModifiedUsernameFieldChange
17-01-11 12:31TerrikateNew Issue
17-01-11 12:31TerrikateFile Added: logs.zip
17-01-11 13:31MrSugarCubeNote Added: 0000840
17-01-11 13:42TerrikateNote Added: 0000841
17-01-11 22:05TerrikateFile Added: sphere_block_again.jpg
17-01-11 22:09TerrikateNote Added: 0000842
17-01-11 23:33MrSugarCubeNote Added: 0000843
17-01-11 23:59TerrikateNote Added: 0000844
19-01-11 16:19TerrikateNote Added: 0000845
19-01-11 17:00MrSugarCubeRelationship addedrelated to 0001868
19-01-11 18:03MrSugarCubeNote Added: 0000846
20-01-11 13:17TerrikateNote Added: 0000850
22-01-11 02:22MrSugarCubeNote Added: 0000853
24-01-11 00:24TerrikateNote Added: 0000863
24-01-11 00:38TerrikateNote Added: 0000864
24-01-11 00:52MrSugarCubeNote Added: 0000865
24-01-11 01:41TerrikateNote Added: 0000867
24-01-11 02:10TerrikateNote Edited: 0000867bug_revision_view_page.php?bugnote_id=0000867#r97
24-01-11 15:18TerrikateNote Added: 0000868
24-01-11 15:27MrSugarCubeStatusnew => closed
24-01-11 15:27MrSugarCubeAssigned To => MrSugarCube
24-01-11 15:27MrSugarCubeResolutionopen => duplicate

Notes
(0000840)
MrSugarCube   
17-01-11 13:31   
The error code indicates that there was not enough memory available to compress the packet.

Did you notice that memory usage was particularly high at the time this happened?
(0000841)
Terrikate   
17-01-11 13:42   
No, but now sphere has been to use 1065MB when it usually did not exceed the 950MB.

If you want to check one more thing ...
(0000842)
Terrikate   
17-01-11 22:09   
I have been blocked again (I'm back to a previous version). If you need some more information this time I made a dump of the entire process before closing. Information about 2GB. About 230MB compressed.
(0000843)
MrSugarCube   
17-01-11 23:33   
The previous version you have switched back to is from 3rd January 2011 (1385?), and doesn't have this problem?
(0000844)
Terrikate   
17-01-11 23:59   
Yes, that is.
(0000845)
Terrikate   
19-01-11 16:19   
After further testing version 3 January and 23 December the problem persists ... so I gather it's just my thing. As you mention the ruling party is more hardware than software, right?.

But wonder if hardware does not strike the typical blue screen and restart the computer. I'll see automatic updates have been made recently. Surprise me was just a RAM problem.

If you know of anything else I'm all ears.

Thanks.
(0000846)
MrSugarCube   
19-01-11 18:03   
It won't be a hardware problem (at least, there's no need to check your RAM or anything :)). Based on the task manager image it appears that the problem is caused by Sphere (for some reason) trying to use more than 2GB of RAM and Windows does not allow this by default.

This could indicate that Sphere has a memory leak or possibly that it is trying to do something that needs this much memory. It could be worth us adding support for using additional memory (3GB or 4GB max depending on 32-bit or 64-bit), although if the problem is a memory leak then it will only buy some extra time before the issue arises.

I don't know what the side effects will be (if any) when enabling support for >2GB memory, but there's a guide at http://www.techpowerup.com/forums/showthread.php?t=112556 [^] if you want to try it yourself at your own risk.
(0000850)
Terrikate   
20-01-11 13:17   
Thx.

Took some time without controlling the use of RAM and so, if before remained constant below 1 GB are now gradually increases without releasing anything at any time.

I told the process use more than 2GB of RAM so we'll know in a moment if it serves as a temporary fix or not to avoid having to restart the server every day.
(0000853)
MrSugarCube   
22-01-11 02:22   
Since issue 0001868 has been fixed (hopefully), it might be worth trying out the next automated build (version 1401) to check if the situation has improved at all.

If you have TooltipCache=0 in your sphere.ini then it is possibly the same issue that you're seeing here.
(0000863)
Terrikate   
24-01-11 00:24   
Yesterday's version continues with the same problem and the last compiled is unplayable, much lag. The server gets to 100% CPU.
(0000864)
Terrikate   
24-01-11 00:38   
Wait for you that the issue is more rare than I thought. I'll tell you that maybe the problem is the equipment itself. It was back to a previous version and is just as bad.
(0000865)
MrSugarCube   
24-01-11 00:52   
Build 1401 didn't fully address issue 0001868 so you'll be better off checking tonights automated build instead (version 1402), or perhaps enable TooltipCache to eliminate that as a possible cause.
(0000867)
Terrikate   
24-01-11 01:41   
(edited on: 24-01-11 02:10)
I tried both, #1401 and #1402 (for few minutes). The issue is that It got 100% cpu after starting the server. It rarely happens. Returning to yesterday's version, still going on but after making a massive disconnect and was well ... Tomorrow I'll tell you how everything went.
(0000868)
Terrikate   
24-01-11 15:18   
All right.

Thanx.