0001745: AsyncNetwork not working - SphereServer BugTracker

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001745

SphereServer

executable - generic

public

04-05-10 19:45

15-11-10 00:45

Reporter

Coruja

Assigned To

MrSugarCube

Priority

high

Severity

major

Reproducibility

always

Status

closed

Resolution

unable to reproduce

Platform

OS Version

Product Version

0.56c Nightly

Target Version

Fixed in Version

Summary

0001745: AsyncNetwork not working

Description

If AsyncNetwork is enabled, newest clients runs fine and older clients get laggy. And with async off, newest clients become laggy and older clients runs fine.
So UseAsyncNetwork=0 makes older clients fine and UseAsyncNetwork=1 makes newest clients fine. But probably theres some problem on UseAsyncNetwork=2 because some clients continues running with 'lag'

// Use asynchronous data sends (changing this setting at runtime may produce unexpected behaviour)
// 0 = Off
// 1 = On
// 2 = On for 4.0.0+ game clients only
UseAsyncNetwork=2

Additional Information

03/05/10 build
MaxPacketsPerTick=50
MaxQueueSize=0
MaxSizePerTick=12000
UsePacketPriority=0

Tags

No tags attached.

Nightly Version

Not Available

Experimental Flags

None

Option Flags

None

Internal Build Number

Attached Files

Relationships

Notes
(0000475) gnomo (reporter) 25-05-10 19:49	Players complain that hangs a few seconds when entering or gate receives magic poison. Tested with r1282 for windows

(0000476) Mirravin (reporter) 25-05-10 20:15 edited on: 25-05-10 20:20	On 6.0.14.3 I also have disconnects and and "WARNING:57:TX Error 11" in console somentimes, than opening a container with many items, also than opening buy list after vendor restocking. internal build #1277, Linux EF_NetworkOutThread ON UseAsyncNetwork=2

(0000611) Terrikate (developer) 05-09-10 16:26	Here it works. The only thing with UseAsyncNetwork 0 or 2 the server doesn't hold for two minutes online, when I have 20+ players online. Not report any fall leaves (crash dump) in the latest versions. I had to try with the version of August 14 to get a crash dump and could only get it with AsyncNetwork 0.

(0000612) Terrikate (developer) 05-09-10 16:29	Here Crash dump report http://www.megaupload.com/?d=OJRAUA82 [^]

(0000745) MrSugarCube (administrator) 04-11-10 12:26	I can't see any problems here, is there still a crash on the latest automated builds? There is also a debug message shown on the latest automated build (with 08000 set on DebugFlags) which you can use to see if there are any clients that don't enter the correct mode. It will look like: x:Switching async mode from 0 to 1.

(0000747) Terrikate (developer) 04-11-10 20:07	I am currently using mode 1 because I'm forcing players to play with a client 7.0.8.2. One of these days I'll try to put the auto mode (2) and tell you.

(0000758) Terrikate (developer) 14-11-10 18:43	Tested here for hours in mode 2 and no problems. I guess the bug was found and resolved on previous versions.

Issue History
Date Modified	Username	Field	Change
04-05-10 19:45	Coruja	New Issue
04-05-10 19:45	Coruja	Nightly Version	=> Not Available
04-05-10 19:45	Coruja	Experimental Flags	=> None
04-05-10 19:45	Coruja	Option Flags	=> None
25-05-10 19:49	gnomo	Note Added: 0000475
25-05-10 20:15	Mirravin	Note Added: 0000476
25-05-10 20:19	Mirravin	Note Edited: 0000476
25-05-10 20:20	Mirravin	Note Edited: 0000476
23-08-10 17:27	MrSugarCube	Priority	normal => high
05-09-10 16:26	Terrikate	Note Added: 0000611
05-09-10 16:29	Terrikate	Note Added: 0000612
04-11-10 12:26	MrSugarCube	Note Added: 0000745
04-11-10 20:07	Terrikate	Note Added: 0000747
14-11-10 18:22	MrSugarCube	Assigned To	=> MrSugarCube
14-11-10 18:22	MrSugarCube	Status	new => feedback
14-11-10 18:43	Terrikate	Note Added: 0000758
15-11-10 00:45	MrSugarCube	Status	feedback => closed
15-11-10 00:45	MrSugarCube	Resolution	open => unable to reproduce