"An unexpected error occured..."
Been plagued with this error since v18.
Dwg.s from others. They have been audited & purged.
Hit OK, and can usually continue without problem or "crash_report.txt" report.
Anyone else experiencing similar?
Comments
-
A fix for such exception, triggered by clicking on the Quad title bar, is included in V18.1.08.
Is this the version you are using?0 -
Version 18.1.08 (x64) revision 51397
0 -
Thanks, so this concerns another exception...
When an exception occurs, and it doesn't lead to an immediate complete crash, the application will indeed create a crash_report.txt log file.
Depending on how the drawing was loaded into BricsCAD, this log file will be placed either in the same folder as the drawing or in the same folder as bricscad.exe (the BricsCAD installation folder).
To investigate and solve this problem it would be really helpful if you could file a support request and attach such crash_report.txt log.
We apologize for this inconvenience and will do the best we can to solve this issue in a timely fashion.Kind regards,
Hans0 -
Thanks.
It did indeed create a crash_report.txt in the Bricscad root folder (not the usual file in the offending dwg's directory, which is odd)
Will submit a support request.
Cheers0 -
Thanks for helping us improve BricsCAD quality.
0 -
Postscript to this issue:
On the most recent occasion, there was NO 'crash_report.txt' anywhere after the "unexpected error" warning.
Yes, I searched entire hard drive.0 -
Per support :
"I have good news: the bug is now fixed for our next update. I was able
to reproduce it with your drawing after hovering the quad so it displays
rollover properties, closing the drawing, opening another drawing, then
it crashes when the rollover quad opens again.
Thanks for reporting the crash!"Kudos to the Bricsys Team for their rapid resolve.
0