Page 1 of 1
Help us solve a bug!
Posted: Thu 22. Mar 2012, 11:23
by Opa
branan wrote:Hi everyone!
We've got a bug that causes the client to crash on shutdown sometimes. It's quite difficult to track down, so we'd like your help narrowing down the situation that causes it. The following information would be helpful:
Which ages you visited during the session, ideally in the order you visited them
Whether you were in any of those ages with someone else, or if you explored alone the entire time
Whether you took the fireflies in Eder Kemo
If you are encountering this issue, the stack trace will contain 0x007D4FB0 on Gehn.6. If you have a stack trace that has that line somewhere in the middle, I'd really love to see it. The more lines that you have below this line, the more useful information is available to me.
This post was originally posted in the GoW forum. Because I noticed, that we also have this bug, it would be nice if you could search for this bug on TOC too. If you close Uru and a stack trace window pops up, please take a look if you can find
0x007D4FB0 in it. If so, post this stack trace here or in
the original thread from the GoW.
Opa
Re: Help us solve a bug!
Posted: Sat 28. Apr 2012, 18:07
by Mystler
You might also help us by sending your log folder (especially the crash.dmp file) from "C:\Users\<Username>\AppData\Local\The Open Cave" (Win7) to support (at) the-open-cave (dot) net.
Re: Help us solve a bug!
Posted: Sun 29. Apr 2012, 10:49
by Scarchu
Is there a way we (users) to see what info is crash.dmp file contains?
Re: Help us solve a bug!
Posted: Sun 29. Apr 2012, 12:28
by Opa
No. The crash.dmp file contains infos about the loction in the code where the error occured. If you wnt to interpret the crash.dmp you need to have the debug symbols (a .pdb file) and you need our source code and MS Visual Studio. Then the file directs you to the line in the code where the error occured.
For short: There is no simple error message in the file,so if you are not known in C++ you can't do something with it.
Opa
Re: Help us solve a bug!
Posted: Wed 27. Feb 2013, 02:35
by NellieBly
Last post was almost a year ago: but if this is still an issue I will keep my eyes open and zip up the logs and trace for you.
Re: Help us solve a bug!
Posted: Wed 27. Feb 2013, 09:53
by Mystler
I unstickied this thread since the stack trace described here is outdated.
Re: Help us solve a bug!
Posted: Fri 1. Mar 2013, 22:55
by Hoikas
I fixed this bug a few months ago, so all's good
Re: Help us solve a bug!
Posted: Fri 1. Mar 2013, 23:17
by McBeam
thank you kind sir where would we be without you!
