Status should not be pending unless issue is assigned and a resolution 
is in progress.  Issue only reported on 2.5 as far as I can tell, let's 
see if it gets reported again for a later version of Python/Tk.  We 
appear to have a workaround for Windows, at least - remove config-
main.cfg and let IDLE recreate it.  Note that IDLE can't 'crash', it's 
pure Python - any crash would be in Python or Tcl/Tk. However, IDLE can 
raise an exception and exit.  If it's an IDLE failure, the traceback 
will be written to the console, so you have to start IDLE from the 
console to see it.

Also, it does sound like the Mac and XP issues are separate problems, 
so please reopen this bug and include a traceback if the failure is seen 
again.