| Quote |
|---|
Miloš Radovanović wrote: Anyway, since you posted this I reintroduced CEF into TB, and first impressions are that history is another major part in solving the slowdown issues. Waiting to see whether TB will leave orphan CEF processes in the background after closing, now that I disabled history monitoring altogether. These can cause major slowdowns if not killed manually before starting TB again. |
It's been almost a month now of using TB with history tracking turned off and CEF turned back on, and I can confidently say that history was a major cause for slowdowns when viewing messages, even more than the CEF cache. I was about to report that, after disabling it, I had no instances of orphan CEF processes, but it happened yesterday... and only once. Before it was a daily occurrence.
It's kind of strange since I had the history set up to only track outgoing messages, but it seems that all folders were being scanned anyway.
Apparently, the history tracker would delay the viewing of messages so much that CEF processes would crash. Yes, CEF is a bit slower than the alternative HTML message viewer, but now we're talking in milliseconds, not seconds or minutes.