Magicians crashing after dying
 

A few of my testers have verified this, as well as myself. Whenever the magicians die, one of two things happen:

1) They die and crash immediately. You can't tell they have crashed but they appear offline to all players. The magician sees a full screen as if nothing has happened, however his screen never updates. If players walk by, mobs walk away, he still sees whatever he saw when he died. The only way to fix is to exit the game by ctrlaltdel or other methods, as quit and camp are unavailable.

2) They die and are able to be rezzed, but that's it. At this point everything from the above applies.

eqemu_error_world, both Isaaru and Shivis are Magicians, no one else throws these errors.

#1 is a desync between the client and server. The result you describe is quite how you know the client has desync'd form the server.

A flood of data from the server to a client like the above errors could easily cause a desync. What rev are you running?

Not at the server atm, but it was setup on the most current revision as of ~12 Jan.

Bump, revision is 2099.

This issue has arisen on my server again, anyone know what could be causing this? It's no longer specific to any one class.

Running 2197

Bump, the cause of this crash still eludes me.

That's a lot of items to sort through..can you verify whether norent items are being used when this happens?


EDIT: That's probably superfluous... You're 'acctid' is changing between 13 and 35. I reckon a guess that the proper 'acctid' for Shivis is neither of the two.

No norent items or attuned items. The only nodrop item equipped is a custom charm (pure stats, no focus/clicky) and epics. The accountids are correct, two separate characters were used in the above example.

This issue is not specific to any specific players, accounts, classes, or races. In any given fight (6 of us) when we all die between 1 and 4 of the characters will experience this issue, and it's completely random which do.

Yep, my bad..I see that now. My eyes saw Shivis all the way down...

I'll see what I can trace back before I leave this evening.

I followed this around a bit and have a few ideas... But, first... Are you running a Linux server?


EDIT: There's something convoluted about what's happening here. There's very few ways to get that warning message. The returned value must be '-1'.
It's almost like you're losing your *item reference between PutItem() and _PutItem().

If you were to add the 'put_slot_id' to the warning message, it should be reporting ''-1.'

I'll dig around some more tonight.

I mispoke above..I meant slot_id reference, not *item. That, or the value is becoming corrupted somehow.

(My brain and hands weren't on the same page when I typed that.)

This is untested, but shouldn't cause any issues:

[putitemtrace.patch - built on rev 2284]
Try this, and the next time the issue comes up, post the log again.

Pretty sure this is the issue and this massive info dump is what's causing the crashes. Just pulled these logs from a fight I did 10-15 minutes ago and the two characters referenced, are the two that crashed.

edit: just saw your message. How do I use that?

Updated logs with the patch in place.

charid 10 and 14 did not crash, charid 96 did crash.

Error_Zone:
Debug_Zone:

This shows that something screwy is going on:


Also, all of your 'failures' appear to be in the inventory bag slot range (251 - 330), which means this segment of code in _PutItem is likely culprit:

Not sure what's going on just yet, but if the con check fails, result is never set to slot_id, and returns the default value of -1..which, of course,
causes the 'Warning' message. It probably also indicates that the inventory bag isn't being populated.

Causes? Unsure at the moment... Someone else might have a better guess.

(Are you using non-container containers, or summoned bags? I'm not completely familiar current items, so don't laugh too hard!)