Wez Furlong e090eb9eae Image decoding is now done in a bg thread ... Continuing from the previous commit, this shifts: * In-memory data -> temporary file * Image decoding -> background thread The background thread asynchronously decodes frames and sends them to the render thread via a bounded channel. While decoding frames, it writes them, uncompressed, to a scratch file so that when the animation loops, it is a very cheap operation to rewind and pull that data from the file, without having to burn CPU to re-decode the data from the start. Memory usage is bounded to 4 uncompressed frames while decoding, then 3 uncompressed frames (triple buffered) while looping over the rest. However, disk usage is N uncompressed frames. refs: https://github.com/wez/wezterm/issues/3263		2023-03-17 11:41:20 -07:00
..
lib.rs	Image decoding is now done in a bg thread	2023-03-17 11:41:20 -07:00
unix.rs	Image decoding is now done in a bg thread	2023-03-17 11:41:20 -07:00
windows.rs	Image decoding is now done in a bg thread	2023-03-17 11:41:20 -07:00