Memory Error: py2.6, wxpy2.8.9.1, win2k3

Hoping someone can help point me in a the right direction in tracking
down using py2.6 and wxpython2.8.9.1 on Win2k3.

Once the initial wx.Frame has been loaded, the system is closed by the
os with the error;

<begin error>
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Time: 4:34:18 PM
User: N/A
Computer: <mycomputer name>
Description:
Faulting application python.exe, version 0.0.0.0, faulting module
unknown, version 0.0.0.0, fault address 0x77542732.
</begin error>

The above entry is from the Windows event log. The window that pops
up says the it is unable to read from this memory location.

Note that the exact same error occurs with the exact same address
regardless of the wxpython script I am running.
- in other words they all create the memory fault.

However;
a) the wxpython demo loads a runs without a problem and the "About"
panel reports running python 2.6 and wxpython 2.8.9.1
b) the exact same script works fine with py2.5 and wxpy 2.8.9.1 on Win2k3
c) the exact same script works fine with py2.6 and wxpy 2.8.9.1 on WinXP Pro
--- even running on the exact same machine as a virtual machine.

The problem seems to be isolated to py2.6 on Win2k3 ... and my code,
but I haven't the vaguest idea where too look for a solution.
FWIW, python is installed in a non-standard directory
C:\devl\python26\ and I also have python 2.5 on the same machine at
location c:\devl\python25.

The only hint I seemed to find is when I created a small application
consisting of a wx.Frame, a single button with an event handler bound
to EVT_IDLE that simple counted and printed each iteration thru the
event handler (ie "print counter +=1") , the frame and button would
get displayed, however, the error would be triggered as soon as the
mouse entered the mainframe. The stdout/stderr window would stop
scrolling and then the error would be displayed.

Any help / advice would be appreciated.

geoff.

···

Date: 10/21/2008

geoff wrote:

The only hint I seemed to find is when I created a small application
consisting of a wx.Frame, a single button with an event handler bound
to EVT_IDLE that simple counted and printed each iteration thru the
event handler (ie "print counter +=1") , the frame and button would
get displayed, however, the error would be triggered as soon as the
mouse entered the mainframe. The stdout/stderr window would stop
scrolling and then the error would be displayed.

Can you share that sample app?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Sorry Robin.
I was a little impatient so reverted back to py2.5
When 2.6.1 and/or wx2.9 is release I will try again.

g.