Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sendq: Allocate of message to player xxx timed out. #27

Closed
Patrikkk-zz opened this issue Jul 25, 2015 · 0 comments
Closed

sendq: Allocate of message to player xxx timed out. #27

Patrikkk-zz opened this issue Jul 25, 2015 · 0 comments

Comments

@Patrikkk-zz
Copy link
Contributor

So apparently when a player gets kicked through any GetData stuff, this happens.
I triggerred the damage cap kick in TShock.
(Also working on a plugin where I kick player at playerdamage packet and same thing happens)

http://puu.sh/jcCg7/d86039bcde.png

and after world is done saving http://puu.sh/jcCh4/9bfc3760b8.png

I debugged to see where the booboo happens. And it's here http://puu.sh/jcBwZ/113872e58b.png

(#isuckwithreports)
Ping pong @tylerjwatson
tylerjwatson added a commit that referenced this issue Jul 30, 2015
@tylerjwatson
Ordered sendq (once more with feeling edition)
8e5d593 
Implemented ordering by use of a lock-and-pulse queue.  This
mechanism does use a syncroot and thus isn't lock free, but
performs far better than the previous iterations.  The
SendData mechanism has been reverted as this method no longer
relies on the allocations of sequences.

CPU has been drastically reduced because of the reduction in
looping in the write threads, and sits between 0-2% with 35
players in live testing.

Fixes Pryaxis/TShock#1049, #27, #26, #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tylerjwatson @Patrikkk-zz