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

  • #008357

  • 0 - None Assigned

  • Needs More Info

Issue Confirmations

  • Yes (0)No (0)
Photo

Map crash with unknown reason :(?

Posted by Gerz on 21 September 2014 - 12:43 AM

Process information:
Command line: map-server.exe
Platform: Windows Server 2008 R2 Enterprise Service Pack 1 (build 7601)
 CPU: x86_64 CPU, Family 6, Model 26, Stepping 5
Application architecture: x86
Compiler: Microsoft Visual C++ 2010 (v1600)
Git: 87125192b6598999b215a35b63de8d3214b2c5e0

Exception:
0xc0000005 EXCEPTION_ACCESS_VIOLATION at location 0x00613F28 reading from location 0xFDFDFDFD

Registers:
eax=00000000 ebx=7efde000 ecx=300b6a5c edx=fdfdfdfd esi=0018ae50 edi=0018af50
eip=00613f28 esp=0018ae50 ebp=0018af50 iopl=0         nv up ei ng nz ac po cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297

Stacktrace:
#0  0x00613F28in <unknown function>
!!failed enumerating symbols!!#1  0x74A5158B in plugin_init+0x509 (<failed enumerating symbols>)
!!failed enumerating symbols!!#2  0x0421EFA0 in HPM_Plugin_AddHook+0xAD750 (<failed enumerating symbols>)
!!failed enumerating symbols!!#3  0x00921C08in <unknown function>
!!failed enumerating symbols!!#4  0x00940001in <unknown function>
!!failed enumerating symbols!!#5  0x0093D1C3in <unknown function>
!!failed enumerating symbols!!#6  0x0095FFC1in <unknown function>
!!failed enumerating symbols!!#7  0x0095EE8Cin <unknown function>
!!failed enumerating symbols!!#8  0x00770DA4in <unknown function>
!!failed enumerating symbols!!#9  0x006C2AFCin <unknown function>
!!failed enumerating symbols!!#10  0x0071C2C9in <unknown function>
!!failed enumerating symbols!!#11  0x00622D83in <unknown function>
!!failed enumerating symbols!!#12  0x0061FD8Din <unknown function>
!!failed enumerating symbols!!#13  0x00605626in <unknown function>
!!failed enumerating symbols!!#14  0x00977CB9in <unknown function>
!!failed enumerating symbols!!#15  0x00977B7Fin <unknown function>
!!failed enumerating symbols!!#16  0x769F338A in BaseThreadInitThunk+0x12 (<failed enumerating symbols>)
!!failed enumerating symbols!!#17  0x77979F72 in RtlInitializeExceptionChain+0x63 (<failed enumerating symbols>)
!!failed enumerating symbols!!#18  0x77979F45 in RtlInitializeExceptionChain+0x36 (<failed enumerating symbols>)

Ind 
changed status to: Started
changed status to: Needs More Info

Some plugin has gone crazy o.o did you recompile the plugins after recompiling the core/map/server?

Nope, the same time? Something wrong with this?

I only used your pl bcooldownrate plugin :(?
	"HPMHooking",
	"dbghelpplug",
	"bCoolDownRate",


I'd recommend trying to recompile everything from scratch (clean build/make clean), also what are you using to show that debug information?

i used "dbghelpplug"

Since the plugin may be compromised, could you provide us with MSVC debug data? You can get it following this guide: http://herc.ws/wiki/...Crash_Debugging (then take a screenshot of the call stack window or copy its contents and paste it to us)

thank you so much Ind, i will try.

best regards.

Hi IND!

Crash again..

maybe problem from your bCoolDownrate plugin?

Link Screenshot

https://www.dropbox.....20.56.png?dl=0

yes seems to be bCoolDownRate...not sure why yet

If crash can be reproduced, may help configure option --enable-sanitize, if memory issue happend, it will dump to stderr error info.