opentibiabr / otservbr-global-archived

Archived, read-only repository. New repository: https://github.com/opentibiabr/otservbr-global
GNU General Public License v2.0
330 stars 331 forks source link

BUG: Server crash after a lot of monsters target you. #2461

Closed gccris closed 3 years ago

gccris commented 3 years ago

Describe the bug

I'm receving a server exception whenever i try to get down from a floor and a lot of monsters try to focus you.

How to Reproduce?

Summon several monsters on a floor below (for example, floor 8), using a normal character, go down the ladder and the error will show up. Error shows up on function Monster::doAttacking of monster.cpp file.

Give us all details to reproduce the behavior:

  1. Create 30+ rats (or any monster) on floor 8 (or any floor)
  2. Using a normal character(not a god), go down on stairs/ladder
  3. All monsters will target you and server will crash
  4. See error : Exception thrown at 0x00007FF612CCD0A0 in otservbr-global-x64.exe: 0xC0000005: Access violation executing location 0x00007FF612CCD0A0.

Logs or errors

Exception thrown at 0x00007FF612CCD0A0 in otservbr-global-x64.exe: 0xC0000005: Access violation executing location 0x00007FF612CCD0A0. image

Expected behavior

All monsters target you correctly.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

Additional context

Add any other context about the problem here.

henriquesameshima commented 3 years ago

It doesn't happen here. Did you change anything in the sources? Would you know if it is in a specific place?

rat

Bipbop69 commented 3 years ago

tested with the screen full of monsters I had no problems

kungen32 commented 3 years ago

Tested full animations, Infernal Demons, Brachiodemons also, there is no bug about this, but, if you have downloaded a version without compiling it, yes you get some of this errors.

travisani commented 3 years ago

Probably your system make crashes because video graphics fault try to do this with new graphcs settings again.

gccris commented 3 years ago

idk what happened, but this error stopped. Maybe it was something related to bad memory position, some weird thing on my machine. After multiples restarts and re builds on source, everythings seems to work fine. I will close it and if happens again, reaise more details and tag to this.