Problem - Client crashing when managing Advloot window

[eqsubi15]

I've been experiencing random crashes lately and I think I've narrowed it down. I just experienced 3 consecutive client crashes all while clicking "Always greed" on random items on the advloot window. This seems to only be happening on one of my characters though, an 85 bard. Not sure what is causing it though.

What program is used to review the .dmp log that it creates?

 

[Amarth]

i would send it to eqmule, regardless, but you can view dmp files in visual studio

 

[eqsubi15]

i would send it to eqmule, regardless, but you can view dmp files in visual studio

Yeah, I plan to do that. Just wanted to review it first and remove any sensitive data though.

 

[Sic]

Yeah, I plan to do that. Just wanted to review it first and remove any sensitive data though.

that's not really how .dmps work - anyone viewing that dmp, assuming the dmp *has* valid information would be able to access that information.

there's no way to "sterilize" the information within - if it has your pspawn information, it has all the information that comes with that

now, to actually debug a live .dmp file (outside of disassembling it) would need access to the VV live symbols server, which only a few have access to

 

[Sic]

think of a dmp file like someone telling a story of a car crash

so I was driving, and then ___, and then ___, and then BOOM

in that story you would have the information about who you are when you say "I" the information on the vehicle when you say "driving" where you were etc etc etc - and hopefully all the information leading up to the crash in an almost "black box" fashion

edit: not all .dmp files are going to have all that information available to it - it depends on a bunch of stuff that I don't understand enough to articulate fairly - but it kind of depends what/where/why the crash occured

 

[eqsubi15]

that's not really how .dmps work - anyone viewing that dmp, assuming the dmp *has* valid information would be able to access that information.

there's no way to "sterilize" the information within - if it has your pspawn information, it has all the information that comes with that

now, to actually debug a live .dmp file (outside of disassembling it) would need access to the VV live symbols server, which only a few have access to

Oh, I see.

 

[Inictus]

It's been happening to me as well on occasions. This happened when I used to use ISBoxer as well (but that's in the rear view mirror now since trying MQ2 ;-)

 

[Grimm68]

I think its EQ issue. i have had it happen even before i started using KA/MQ