Omer Zak wrote: >On Wed, 2006-02-08 at 16:01 +0000, Baruch Even wrote: > > >>Omer Zak wrote: >> >> >>>The evidence points at some process, unknown to me, which gets scheduled >>>in Tkinter's main loop, and which takes about 1sec. While this process >>>is executing, the GUI is unresponsive and my own processes execute later >>>than their scheduled times. >>> >>>Any advice how to find that process and figure out what it does and why? >>> >>> >>I'd start with stracing the python process to try and see if it is >>something wrong or maybe there is a sleep(1) command done there. >> >> > >There were no sleep() calls. strace was not useful. > > Probably not relevant - but just to make sure - do you run your application from interactive mode (e.g. from the interpreter or with python -i)?
If I recall correctly, in interactive mode, the tk event loop does not run in a seperate thread, but uses some trick in the interpreter loop to run the GUI when your'e not typing (so your missing process might be python itself).
