SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001907SphereServerexecutable - linux buildpublic06-02-11 05:2602-11-14 11:31
ReporterMirravin 
Assigned ToXuN 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version0.56c Nightly 
Nightly VersionAutomated (specify build number)
Experimental FlagsNetworkOutThread
Option FlagsNone
Internal Build Number1411
Summary0001907: Flushing data for client.
DescriptionRegularly, when I started using build #1393(and now, on build #1411) instead of build #1385(not occured) I have logs, extended by many "Flushing data for client." messages.
Usually it occurs after a client freeze. Examples are attached(all from build #1411).
Old issue:
http://tracker.sphere.torfo.org/bugs/view.php?id=1843 [^]
Steps To Reproduce
Additional InformationEF_NetworkOutThread ON
UseAsyncNetwork=2
UsePacketPriority=1
UseExtraBuffer=1

TooltipMode=1
TooltipCache=0
TagsNo tags attached.
Relationships
Attached Filestxt example1.txt (1,143) 06-02-11 05:26
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=53&type=bug
txt example_2_classic.txt (568) 06-02-11 05:26
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=54&type=bug
txt example3_classic.txt (442) 06-02-11 05:27
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=55&type=bug
txt example_4_possible_mass_crash.txt (3,844) 06-02-11 05:27
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=56&type=bug
Issue History
Date ModifiedUsernameFieldChange
06-02-11 05:26MirravinNew Issue
06-02-11 05:26MirravinFile Added: example1.txt
06-02-11 05:26MirravinFile Added: example_2_classic.txt
06-02-11 05:27MirravinFile Added: example3_classic.txt
06-02-11 05:27MirravinFile Added: example_4_possible_mass_crash.txt
06-02-11 05:43MirravinNote Added: 0000898
18-02-11 19:19MirravinNote Added: 0000938
18-02-11 19:20MirravinNote Edited: 0000938bug_revision_view_page.php?bugnote_id=0000938#r150
02-11-14 11:31XuNNote Added: 0002549
02-11-14 11:31XuNStatusnew => closed
02-11-14 11:31XuNAssigned To => XuN
02-11-14 11:31XuNResolutionopen => fixed
02-11-14 11:31XuNFixed in Version => 0.56c Nightly

Notes
(0000898)
Mirravin   
06-02-11 05:43   
Experimental=01|08|010000|0800000|08000
OptionFlags=08|0200|080|02000
(0000938)
Mirravin   
18-02-11 19:19   
(edited on: 18-02-11 19:20)
I found a way to reproduse this issue on version #1419 Linux. Unfortunately, Reproducibility is not 100% for me, but about 50%.
1) Login to server.
2) Disable and enable the network card.
3) Try re-login, account already in use. OK.
4) Wait about a 5 minites. Nothing interesting.
5) But... After this, in colsole:
20:07:c7:Frozen client connection disconnected.
20:07:DEBUG:c7:Client being closed by read-thread
20:07:DEBUG:c7:Flushing data for client.
20:07:DEBUG:c7:Flushing data for client.
...
20:07:DEBUG:c7:Waiting for data to be flushed.
20:07:DEBUG:c7:Flushing data for client.
...
Account is complitely free while flushing, we can re-login without a problem, but this NOT stop flushing for old "phantom" client.
After a time flushing stops:
...
20:20:DEBUG:c7:Flushing data for client.
20:20:DEBUG:c7:Client being closed by write-thread
20:20:DEBUG:c7:Client being closed by write-thread
20:20:DEBUG:c7:Client is being cleared since marked to close.
20:20:DEBUG:c7:Clearing client state.
20:20:c7:Client disconnected [Total:11] ('IP1')

So, this bug occurs, whan the client is disconnected, as inactive socket.
(0002549)
XuN   
02-11-14 11:31   
Network Settings should be disabled, they are not working good.