(fixed) Leaky eot_te queue?
Moderator: Sophia
Forum rules
Please read the Forum rules and policies before posting. You may
to help finance the hosting costs of this forum.
Please read the Forum rules and policies before posting. You may

- Gambit37
- Should eat more pies
- Posts: 13771
- Joined: Wed May 31, 2000 1:57 pm
- Location: Location, Location
- Contact:
(fixed) Leaky eot_te queue?
I just got a crash on my modified DM dungeon: "Leaky eot_te queue [Type 4 Data 186a4 0]". I've not seen this before. Is that an error that means something significant I should be aware of?
- Sophia
- Concise and Honest
- Posts: 4306
- Joined: Thu Sep 12, 2002 9:50 pm
- Location: Nowhere in particular
- Contact:
Re: Leaky eot_te queue?
Were you testing it in ESB's interactive mode?
Can you give me steps to reproduce it?
Can you give me steps to reproduce it?
- Gambit37
- Should eat more pies
- Posts: 13771
- Joined: Wed May 31, 2000 1:57 pm
- Location: Location, Location
- Contact:
Re: Leaky eot_te queue?
This was just playing the dungeon normally, not through ESB mode. I've not been able to reproduce it so far, I'll see if I can first.
- Sophia
- Concise and Honest
- Posts: 4306
- Joined: Thu Sep 12, 2002 9:50 pm
- Location: Nowhere in particular
- Contact:
Re: Leaky eot_te queue?
It actually does. That's pretty good confirmation of what I thought was the problem.
When you fall down a pit, the game is temporarily locked, which includes message delivery. DSB was regarding a message in the end of tick timer event (i.e., eot_te) queue being undelivered as a leak, since end of tick messages should be delivered immediately... but it would also be undelivered if messages were locked. That is why you got that error.
When you fall down a pit, the game is temporarily locked, which includes message delivery. DSB was regarding a message in the end of tick timer event (i.e., eot_te) queue being undelivered as a leak, since end of tick messages should be delivered immediately... but it would also be undelivered if messages were locked. That is why you got that error.