Robin,
Hi Robin,
...
Probably not, this is lower-level than those libraries. It's part of the core of how Windows works, but I don't know enough to know what to do about it. Perhaps there is some resource problem on the system and so it's not able to allocate additional window handles or something?
BTW, after looking at the code a bit more I realized that there are actually two errors above, not just one. The "wxWindowClassNR" is probably a frame or panel, and the "Edit" is a wx.TextCtrl as I said before. But it's the same basic failure under the covers, the CreateWindowEx API is failing.
googled a bit on resource issues with XP and came accross the "application verifier" (AV) tool from Microsoft.
http://www.microsoft.com/downloads/details.aspx?FamilyID=c4a25ab9-649d-4a1b-b4a7-c9d8b095df18&displaylang=en
This is usable on XP and higher (tried it on XP and Win 7).
It has a setting to test an application with "Low resources simulation", so I did a few tests.
- Python command line is fine
- Python and Idle crashes (hard, no exception shown)
- wxPython demo crashes (hard, no exception shown)
- my own application crashes - exception MemoryError during the import/initialization of model.py (SQLAlchemy)
After using AV don't forget to remove whatever .exe you monitor with it from it's list otherwise it keeps on monitoring the .exe even if AV is not running.
It would be nice if the crashes would be a bit "more user friendly", but this is probably so low down in the system that this is more an MS Windows issue then anything else.
Anyhow all this is just FYI - find it interesting and it confirms/points to a resource problem on the users machine.
Werner
···
On 25/03/2010 22:44, Robin Dunn wrote:
On 3/25/10 2:11 AM, werner wrote: