Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #008277

  • 0 - None Assigned

  • Invalid

Issue Confirmations

  • Yes (0)No (0)
Photo

memory manager

Posted by Break San on 23 July 2014 - 03:07 PM

Bug that closes the map server.
emulator: https://github.com/H...1b780a9aeeb8ccc

br [Doo]

Posted Image

Update your emulator  :unsure:

You should always say what GitHash your server is currently on :P

changed status to: New

You should always say what GitHash your server is currently on :P

Doesn't the link by @topicstarter says it?
https://github.com/HerculesWS/Hercules/tree/88da261c4cf6f984252adb46a1b780a9aeeb8ccc
88da261c4cf6f984252adb46a1b780a9aeeb8ccc => July 2013

Atualize seu emulador  :unsure:


Sorry I did not specify which.
More current emulator does not use it because the switch does not work.
So I have to use an older emulator.
Know how to solve that bug?

This shouldn't be handled here, this issue probably was already solved. If you need help on how to apply the fix you should use the forums not the tracker.
Thank you for reporting.

pan 
changed status to: Invalid

This memory manager error has already been resolved?

This is not a memory manager error, it's probably related to an old chunk of code. Without more information regarding what you were doing when the crash occurred, the rest of the messages from your server and a core dump there isn't much we can do to know what happened. You should try to reproduce this issue in a newer revision and if it happens again post here, then we'll be able to help, otherwise it'll be just like shooting in the dark.