SUPPORT REQUEST NOT WORKING - CRASH REPORTS

STEVEN SANDHORST

For some reason I can't log a support request with Bricsys, so I'll post this in the Forum!

Whenever I open a drawing file by double-clicking it in Windows Explorer, do some editing, save, then close BricsCad (version 12.2.12), I get a crash_report.txt file in the same directory as the drawing!  This is what it says:

--------------- 03-07-2012 08:46:00 --------------- v12.2.12.26523 ---------------
Unhandled Exception:
ACCESS_VIOLATION (C0000005) in module wxgui.dll at 001B:5E538175
Registers:
EAX=01A76948  EBX=00000001  ECX=00000000  EDX=5E5BC470  ESI=00000000  EDI=00F6F390  EBP=00000000  ESP=0013F378  EIP=5E538175  FLG=00010246  CS=001B  DS=0023  SS=0023  ES=0023  FS=003B  GS=0000

Call stack:
empty..

Daniel Eiszele

 I can confirm this behaviour.  I haven't upgraded to 12.2.12 yet but the log file is created upon exit regardless of whether I edit or not.  I will submit a support request.

Regards,

Robt Deans

Curious, I've just recently noticed the same behavior w/ v12.2.12

Patrik Sparrman

Strange you mentioning this because I just got this without the app crashing.

--------------- 04-07-2012 13:51:04 --------------- v12.2.11.26501 ---------------
Unhandled Exception:
ACCESS_VIOLATION (C0000005) in module wxgui.dll at 001B:5E538155
Registers:
EAX=02B486C0  EBX=00000001  ECX=00000000  EDX=5E5BC450  ESI=00000000  EDI=01646748  EBP=00000000  ESP=0012F2B8  EIP=5E538155  FLG=00010246  CS=001B  DS=0023  SS=0023  ES=0023  FS=003B  GS=0000

Call stack:
empty..

Hans De Backer

We have been trying to reproduce this issue, but did not yet succeed so far.
A scenario that allows reproduction would be helpful and much appreciated...
Meanwhile we will give it some more trying

Richard Webb

As another data point, I have not experienced the spurious crash report generation. Running Ver 12.2.12 (build 38217 rev 26523) under Win 7 Pro (64 bit) and an Nvidia Quadro 2000M graphics adapter. 

1. Navigate to a drawing folder using Windows Explorer.

2. Double-click a drawing file to launch Bricscad and open the drawing.

3. Edit, save, exit Bricscad.

4. No crash_report.txt in that folder/sub-directory.

I *do* have a one that was generated from an earlier version in the Bricscad installation directory:

--------------- 16-04-2012 10:32:57 --------------- v12.1.22.25453 ---------------
Exception:
ACCESS_VIOLATION (C0000005) in module at 0023:63BFAAE0

That (if I recall the timing correctly) was shortly after I had started using the new Win7 box and it's quite possible that I had not fully applied all of the manufacturer's recommended patches/updates/driver-fixes at that time. Nothing unusual since then.

David Laviana

Mr Hans De Backer -

I was going to file a support request on this issue, but I see I'm not alone in seeing these odd "crash reports".  I just moved from V12.1.22  to V12.2.12, and never had this occur under the old version.  The text of my reports are exactly the same as the ones posted here.  It doesn't matter if you do anything; I opened Bricscad tonight to check the version number and then exited the program.  A crash report was posted in the program directory as I exited.  If I'm editing a drawing, the report is left in the directory of the drawing.  I have my copy of Bricscad on my work and home computers, and the messages are the same in both locations.  I haven't had any actual problems when working with the program; everything works properly.  For the record, I'm running Windows XP Pro, SP3, and pretty much up to date on critical updates.

If I see anything that might help track this down I'll post an update.  Good luck on tracking this down, it probably won't take you guys too long.  However, keep in mind the curse of programming - "There's always one more bug......"

Daniel Eiszele

I submitted a support request yesterday and the analyst was unable to reproduce the error.  However the programmers have narrowed the issue to some recently added code through the crash report and are looking into the issue.  It was present from at least 12.2.9

Hans De Backer

Update: 
during application shutdown, all user interface items (windows, combo boxes, toolbars, etc...) are destroyed. Once an item is destroyed, any attempt to access it, will result in an access-violation: it is not possible to access something that no longer exists...

The sequence of destruction varies depending on enabled/ disabled toolbars, status bar items, dialog layout, etc... hence this access violation can occur on some machines and not on others.

We have identified the offending user interface item and are working on a fix.

For your information: this exception is harmless as it happens while the application exits after all data has been saved, but of course we want the application exit to be clean.

STEVEN SANDHORST

This problem still persists in version 12.2.14.  The release notes imply that it is fixed, but it still happens when I double-click the drawing file in windows explorer to open BricsCad and the drawing.

Daniel Eiszele

Unfortunately I have to concur.  I have just finished reinstalling my system from scratch and as Steven states the issue is still apparent even on a completely clean computer.  I will update the support request accordingly.

Regards,

Daniel Eiszele

 Support has communicated that this issue is fixed in their internal builds; so it should make it into the next maintenance release!

Greg Skelhorn

I sure do have a lot of these dump files lying around.... Is there a variable or setting to prevent creation of them? Sure would be nice to have this fixed.

Luc De Batselier

We are preparing a maintenance release with a fix right now.
@Greg check QAFLAGS , it has a setting for dump files

Greg Skelhorn

Thanks Luc... not sure how I missed seeing that one! :-)

Johan Stakenborg

I have the samen problem.

Since I have 12.2.12, I have now12.2.14, I have crash reports.

Even When I open a drawing , maked with Bricscad

Bryan Tuenter

@Daniel Eiszele:

Unfortunately I have to concur.  I have just finished reinstalling my system from scratch and as Steven states the issue is still apparent even on a completely clean computer.  I will update the support request accordingly.

Regards,

same problem here...

--------------- 14-08-2012 15:24:36 --------------- v12.2.14.26665 ---------------

Unhandled Exception:

ACCESS_VIOLATION (C0000005) in module wxgui.dll at 001B:5E538145

Registers:

EAX=024C26E0  EBX=00000001  ECX=00000000  EDX=5E5BC480  ESI=00000000  EDI=024FA040  EBP=00000000  ESP=0012F2B8  EIP=5E538145  FLG=00010246  CS=001B  DS=0023  SS=0023  ES=0023  FS=003B  GS=0000

Call stack:

empty..[code]PASTE CODE HERE[/code]

STEVEN SANDHORST

Version 12.2.17-1 has fixed the problem - YAY! 

Daniel Eiszele

 +1

But I did note that the QAFlags setting for creating "crash dump files" is off by default; so, should you actually want them, you will have to turn this setting back on.