Tkinter and thread. out of stack space (infinite loop?)

Question

I\'m experimenting with Tkinter and the threads mechanism. Can anyone explain why this raises the exception:

 out of stack         


        

Answer 1

You have a couple of fatal flaws in your code. For one, you simply can't write code that touches tkinter widgets from more than one thread. You are creating the root window in the main thread, so you can only ever directly access widgets from the main thread. Tkinter is not thread safe.

The second problem is that you have an infinite loop that is constantly appending to the text widget. It has no choice but to eventually run out of memory.

To solve your problem you should:

1. not have an infinite loop that forever appends to the text widget
2. not access any widgets from more than a single thread

If you want to run a function once a second, there are better ways to do that than with threads. In short:

def do_every_second():
    cont.insert("end", str(n) + "\n")
    root.after(1000, do_every_second)

This will cause do_every_second to do whatever it does, then arranges for itself to be called again one second in the future.

Answer 2

The error is correct - there's an infinite loop on one of the tkinter elements. The thread module has nothing to do with it. The specific line causing the error:

cont.insert('end', str(n)+"\n")

Since cont is a tkinter element, you can not run it in your infinite while loop. To do what you want, you would need to print to the console instead. This can be demonstrated if you replace the offending line with a simple:

print(str(n)+"\n")

Edit: If you truly want to achieve the same effect you originally intended, this post deals with a potential alternative.

Edit2: I would assume the exception is a design choice by the tkinter library (although I'm no expert). This would make sense since tkinter already uses an infinite loop for its event loop. I would imagine an infinite loop would prevent tkinter from ever drawing the changes to the screen and instead the libraries authors chose to throw an exception instead. A print should work since there's nothing new to draw, plus it's in it's own thread allowing tkinter's event loop to continue.