Opened 13 years ago

Closed 12 years ago

#10082 closed defect (fixed)

wxPython APPCRASH under windows vista 64 bit using python 2.6.

Reported by: asnast Owned by: robind
Priority: critical Milestone:
Component: wxPython Version: 2.8.x
Keywords: Cc: bitmonster@…
Blocked By: Blocking:
Patch: no


When i try and run a very simple wxpython app:

import wx
app = wx.PySimpleApp()
frame = wx.Frame(None, -1, "Hello World")

The window pops up but crashes when i mouse over it. I get the following report:

Problem signature:

Problem Event Name: APPCRASH
Application Name: python.exe
Application Version:
Application Timestamp: 48e49612
Fault Module Name: comctl32.dll_unloaded
Fault Module Version:
Fault Module Timestamp: 4791a629
Exception Code: c0000005
Exception Offset: 73fa5a6e
OS Version: 6.0.6001.
Locale ID: 1037
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

This doesn't happen with python 2.5.2.

Thanks, Alex Snast

Change History (7)

comment:1 Changed 13 years ago by bitmonster


Same problem here with wxPython2.8-win32-unicode- under Vista Ultimate x64. Simple applications crash as soon as one moves the mouse onto their window. More complicated applications seem to work fine. Even the demo crashes if you move the mouse onto the splashscreen. If you leave the mouse outside the spashscreen and let it disappear, the demo seams to run fine.

comment:2 Changed 13 years ago by bitmonster

  • Cc bitmonster@… added

comment:3 Changed 13 years ago by thorsten

Same here: Python 2.6, Vista SP1 32bit, wxPython - as soon as the mouse enters the application (whatever that is, also the demos) - Python.exe crashes...

comment:4 Changed 13 years ago by robind

  • Owner set to robind
  • Status changed from new to accepted

comment:5 Changed 13 years ago by robind

This may be the same problem as #10122...

comment:6 Changed 12 years ago by weaver4

  • Priority changed from normal to critical

Doesn't a bug that makes the product completly unusable in Vista or Windows 7 deserve a priority greather than "normal". It has been 5 months since this bug was reported.

comment:7 Changed 12 years ago by vadz

  • Resolution set to fixed
  • Status changed from accepted to closed

I believe this is the same as #10203 and so should be fixed in 2.8.10.

Note: See TracTickets for help on using tickets.