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)