[DiscordArchive] What leads you to believe player object was deleted from that crashlog?
[DiscordArchive] What leads you to believe player object was deleted from that crashlog?
Original source
What leads you to believe player object was deleted from that crashlog?
rektbyfaith
01-09-2025, 02:54 PM #1Archived author: Takenbacon • Posted: 2025-01-09T14:54:42.050000+00:00
Original source
What leads you to believe player object was deleted from that crashlog?
Original source
Looks more like a form of memory corruption to me
rektbyfaith
01-09-2025, 02:54 PM #2Archived author: Takenbacon • Posted: 2025-01-09T14:54:55.490000+00:00
Original source
Looks more like a form of memory corruption to me
Original source
Not that the whole player object data is bad
rektbyfaith
01-09-2025, 02:55 PM #3Archived author: Takenbacon • Posted: 2025-01-09T14:55:14.676000+00:00
Original source
Not that the whole player object data is bad
Original source
I suppose it could be possible if there's a spell that forces a logout or something odd?
rektbyfaith
01-09-2025, 03:01 PM #4Archived author: Takenbacon • Posted: 2025-01-09T15:01:53.340000+00:00
Original source
I suppose it could be possible if there's a spell that forces a logout or something odd?
Original source
I don't have direct evidence that this is the case in the crash. But what makes you think that the whole object was not deleted in that crash log? I think Player:
rocessSpellQueue is one of the first (well almost) functions called in Player::Update. I believe in most cases it is the first function that interacts with a container. This makes me think that we would encounter such crash if we were using a deleted player object.
rektbyfaith
01-09-2025, 03:20 PM #5Archived author: walkline • Posted: 2025-01-09T15:20:34.214000+00:00
Original source
I don't have direct evidence that this is the case in the crash. But what makes you think that the whole object was not deleted in that crash log? I think Player:rocessSpellQueue is one of the first (well almost) functions called in Player::Update. I believe in most cases it is the first function that interacts with a container. This makes me think that we would encounter such crash if we were using a deleted player object.
Original source
It could be, I would lean more into possibly a queued spell causing a logout rather than somehow a lingering reference in the map container though, that would be exceptionally difficult to do
rektbyfaith
01-09-2025, 04:03 PM #6Archived author: Takenbacon • Posted: 2025-01-09T16:03:06.956000+00:00
Original source
It could be, I would lean more into possibly a queued spell causing a logout rather than somehow a lingering reference in the map container though, that would be exceptionally difficult to do
Original source
But with all these janky mods doing weird ass stuff who knows anymore
rektbyfaith
01-09-2025, 04:03 PM #7Archived author: Takenbacon • Posted: 2025-01-09T16:03:42.795000+00:00
Original source
But with all these janky mods doing weird ass stuff who knows anymore
Original source
What the heck? Is it a bugged linked list implementation for cases when it's the beginning or the end of the list, or did I misunderstand something? https://github.com/azerothcore/azerothco...List.h#L54
rektbyfaith
01-09-2025, 11:44 PM #8Archived author: walkline • Posted: 2025-01-09T23:44:59.048000+00:00
Original source
What the heck? Is it a bugged linked list implementation for cases when it's the beginning or the end of the list, or did I misunderstand something? https://github.com/azerothcore/azerothco...List.h#L54
Original source
I learned that the head and tail in this LinkedList implementation are "sentinel nodes". They hold no values and only mark the beginning and end of the list, so they aren't considered to be part of the list
rektbyfaith
01-10-2025, 10:27 AM #9Archived author: Sogla • Posted: 2025-01-10T10:27:33.640000+00:00
Original source
I learned that the head and tail in this LinkedList implementation are "sentinel nodes". They hold no values and only mark the beginning and end of the list, so they aren't considered to be part of the list
1 Guest(s)
1 Guest(s)