Intermittent Win7 Application Error, Exception code: 0xc0000005

wxPython Users
1

Hello –

I’m getting an intermittent Application Error crashing my app on Win7. It showed up after I added code for an OnPaint event.

Here’s the error data:

Faulting application name: img2track.exe, version: 0.0.0.0, time stamp: 0x514e2c2f

Faulting module name: wxmsw30u_core_vc90.dll, version: 3.0.0.0, time stamp: 0x52bea66f

Exception code: 0xc0000005

Fault offset: 0x0003f549

Faulting process id: 0x1fc

Faulting application start time: 0x01cf47bc62515f48

Faulting application path: C:\Users\Davi\DOCUME~1\Knitting\IMG2TR~3\dist\img2track.exe

Faulting module path: C:\Users\Davi\AppData\Local\Temp_MEI32122\wxmsw30u_core_vc90.dll

Report Id: f365e182-b3af-11e3-898d-0022680e1bfa

A search on the Exception code suggests it may be an Access Violation. I have not seen this error while running other software on that machine.

I am trying to whittle down the code to see what might be causing the problem, but I have to play with the program for a while before the error occurs – I cannot reproduce it reliably.

Is it likely a bug in wxWindows?

Should I be running hardware tests?

Sure could use a hint. Thanks,

–Davi

2

Davi P wrote:

I'm getting an intermittent Application Error crashing my app on Win7.
It showed up after I added code for an OnPaint event.

Here's the error data:

Faulting application name: img2track.exe, version: 0.0.0.0, time
stamp: 0x514e2c2f
Faulting module name: wxmsw30u_core_vc90.dll, version: 3.0.0.0, time
stamp: 0x52bea66f
Exception code: 0xc0000005
Fault offset: 0x0003f549
Faulting process id: 0x1fc
Faulting application start time: 0x01cf47bc62515f48
Faulting application path:
C:\Users\Davi\DOCUME~1\Knitting\IMG2TR~3\dist\img2track.exe
Faulting module path:
C:\Users\Davi\AppData\Local\Temp\_MEI32122\wxmsw30u_core_vc90.dll
Report Id: f365e182-b3af-11e3-898d-0022680e1bfa

A search on the Exception code suggests it may be an Access Violation.
I have not seen this error while running other software on that machine.

Yes, that's what C0000005 is.

I am trying to whittle down the code to see what might be causing the
problem, but I have to play with the program for a while before the
error occurs -- I cannot reproduce it reliably.

Is it likely a bug in wxWindows?

It's almost impossible to tell if you can't reproduce it. Generally, in
a case like this, my suspicion is that your code is doing something in
an unexpected way that wxWindows could have caught but didn't. That is,
it's likely to be a problem in your code that triggers a crash in
wxWindows, but there's really not enough information here to dig any
deeper. The fact that it happened after a code change is very
significant, because you can start focusing directly on that new code.

You may need to add some logging so you have a trace of activity so you
can spot a trend. I see this is a frozen executable; does it happen on
a development machine as well?

···

--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

3

Thanks for the reply, Tim.

I changed wx.AutoBufferedPaintDC to wx.PaintDC, and haven’t seen any more crashes.

After other changes, I tried AutoBufferedPaintDC again, but instead of crashing it just doesn’t paint anything on WIn7. (On OSX, an adjacent wx.StaticBitmap disappeared as well.)

I develop on OSX, then build the .exe on Win7 for testing on that platform. I didn’t have crashes on OSX.

Hope this info is useful if others see similar crashes. I did several searches, and didn’t find any similar reports.

I thought the offset might be enough to locate a problem, but I guess it’s hard to debug if it can’t be reproduced.

Thanks again,

–Davi

···

On Tuesday, March 25, 2014 11:31:23 AM UTC-5, Tim Roberts wrote:

Davi P wrote:

I’m getting an intermittent Application Error crashing my app on Win7.

It showed up after I added code for an OnPaint event.

Here’s the error data:

Faulting application name: img2track.exe, version: 0.0.0.0, time

stamp: 0x514e2c2f

Faulting module name: wxmsw30u_core_vc90.dll, version: 3.0.0.0, time

stamp: 0x52bea66f

Exception code: 0xc0000005

Fault offset: 0x0003f549

Faulting process id: 0x1fc

Faulting application start time: 0x01cf47bc62515f48

Faulting application path:

C:\Users\Davi\DOCUME~1\Knitting\IMG2TR~3\dist\img2track.exe

Faulting module path:

C:\Users\Davi\AppData\Local\Temp_MEI32122\wxmsw30u_core_vc90.dll

Report Id: f365e182-b3af-11e3-898d-0022680e1bfa

A search on the Exception code suggests it may be an Access Violation.

I have not seen this error while running other software on that machine.

Yes, that’s what C0000005 is.

I am trying to whittle down the code to see what might be causing the

problem, but I have to play with the program for a while before the

error occurs – I cannot reproduce it reliably.

Is it likely a bug in wxWindows?

It’s almost impossible to tell if you can’t reproduce it. Generally, in

a case like this, my suspicion is that your code is doing something in

an unexpected way that wxWindows could have caught but didn’t. That is,

it’s likely to be a problem in your code that triggers a crash in

wxWindows, but there’s really not enough information here to dig any

deeper. The fact that it happened after a code change is very

significant, because you can start focusing directly on that new code.

You may need to add some logging so you have a trace of activity so you

can spot a trend. I see this is a frozen executable; does it happen on

a development machine as well?

–
Tim Roberts, ti...@probo.com

Providenza & Boekelheide, Inc.