Comment 8 for bug 29260

If somebody who gets the issue want to track what happens maybe getting a gdb backtrace of what it is doing could be useful. Using sysprof would give the details of where it's spending cpu