Closed sixpoints closed 2 years ago
After the reader finishes loading, the cpu usage should be lower.
After the reader finishes loading the image and waiting for a few minutes, the cpu usage is still high(about 20%).
Also no more log in the rolling.log during high cpu usage after loading.
This should be fixed in the latest preview, let me know if it still happens
Device information
Steps to reproduce
Expected behavior
After the reader finishes loading, the cpu usage should be lower.
Actual behavior
After the reader finishes loading the image and waiting for a few minutes, the cpu usage is still high(about 20%).
Other details
Also no more log in the rolling.log during high cpu usage after loading.