MemoryHole should fork its busy work below UI priority

Issue #53 new
Ryan Macnak
created an issue

So the UI doesn't lock up.

Comments (1)

  1. Ryan Macnak reporter

    So most of the time it does this, except that for a newly-opened repository most of the source mirrors are computed as a side effect of generating the UI, which happens inside the UI thread. Even hoisting this outside the UI thread and only installing the fragments after they are generated doesn't seem to help. Maybe most of the time is in fact in FFI calls to Mercurial, which block the whole VM, although I would have expected most of the time to be in the parser, which should yield to IO events and the UI thread.

  2. Log in to comment