Added a little debugging logic on my own, and watching the logs. One factor that seems to be present: multiple refresh threads per service running at once. Apparently, Facebook and Twitter start refreshes, and then in the middle of the refresh two more refresh threads get started. After that, all you get in the logs are attempts by the dispatcher to exit. It's in deadlock, because it can't get past the "with _exit_lock:". (I added a debug statement to tell me right when it enters terminate().)
It's not just that situation, though. Just now, I got it to deadlock with just the two update threads (one per service). Oddly, it seems too easy to get 4 update threads running. It seems like I do one refresh request, and the dispatcher records handling 2 refresh requests, with pretty much the same sequence of log entries (i.e. not just random chance that a timer ran out right when I clicked refresh). I wonder if there's a race condition there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171745 Title: Timeline doesn't refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1171745/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
