Simply running it in a tight loop is enough to cause crashes if you have a fast moving application running (ie: glxgears
)
This looks a major blocker for 0.13.
this fixes the problem by not using threading for info processing (temporary workaround)
Relief: was easy enough to identify by trimming the work done by xpra info
to narrow things down, fixed in r6525.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/573