1 Attachment(s)
SERIOUS ERROR Report....SO useless
Remember when we used to be able to actually send an error report? Maybe we never heard anything back, but at least we could send it.
Now, instead, we get sent to a webpage that merely lists 400 plus questions/answers that may or may not have anything to do with what we're dealing with.
HOW HELPFUL IS THAT!!!?????
My most recent error:
Attachment 121752 Access violation exception at 0x00007FF70C28917A
Re: SERIOUS ERROR Report....SO useless
Re: SERIOUS ERROR Report....SO useless
Re: SERIOUS ERROR Report....SO useless
It's fix is in the pipeline but so is Christmas :(
Re: SERIOUS ERROR Report....SO useless
Twenty weeks until Christmas :D
Re: SERIOUS ERROR Report....SO useless
Thanks a bunch for that reminder Jon :banned:
Re: SERIOUS ERROR Report....SO useless
;))
Ron, somewhere on the forum there is a post from Xara support confirming the problem and that it needs to be fixed asap.
Re: SERIOUS ERROR Report....SO useless
Re: SERIOUS ERROR Report....SO useless
Quote:
Originally Posted by
Jonopen
;))
Ron, somewhere on the forum there is a post from Xara support confirming the problem and that it needs to be fixed asap.
Oh, ok. Thanks Jonopen. And thanks Steve. I watched the video.
Re: SERIOUS ERROR Report....SO useless
It's still better than Windows 10 Setup's "Something happened" error message :-O ;))
But I get what you're saying. It could be more verbose
That error says that the program tried to access something (a variable, an object etc.) that's located at memory address 0x00007FF70C28917A and failed. Maybe because the "thing" was improperly scoped. Xara programmers might know the addresses of different portions of the program and could derive what the message relates to. (Or maybe they need a dump file, I don't know. My knowledge of programming is a bit limited. In that case, the error message would be a bit useless without a dump file to debug it)
Re: SERIOUS ERROR Report....SO useless
I think the point is that the error report that used to be sent to xara with that info, no longer works....
a message that is more verbose may be worse, because it may be misleading if it is wrong about the assumed error; the program does not 'know' why the memory addressing failed
Re: SERIOUS ERROR Report....SO useless
Having a more verbose report might help with looking it up on the knowledge base ;))
Re: SERIOUS ERROR Report....SO useless
but there is nothing to look up in the case of a memory exception is there?
unless you have and understand the log you don't know what you are dealing with exactly and niether will the help files
these error messages are not meant for users; programmers, by and large, don't like verbosity; they prefer concise ;)
Re: SERIOUS ERROR Report....SO useless
Hey Guys!
This issue has been raised twice already, I don't think there is any sense of contemplating how useful is it that it doesn't work at the moment - so I will just go ahead and close this thread.
-> We have it in our pipeline, just be patient, we will get this sorted! ;)
Cheers!