Comment 5 for bug 556290

Technically the application *is* not responsive, it is not running the main loop and is not processig events for prolonged periods. This is a side effect of bad design and too
much processing that is performed inside event handlers. I talked with Mvo and am in progress of working on a proof-of-concept rewrite of the backend/processing to be asynchronous. I'll be posting updates to this bug report.

Side note: there are many separate places that need fixing. The one visible here could also be related to gtk treeview performance.