![]() The reason for these strategies is to display a page as soon as possible and to buffer the comic for smooth reading. That also uses CPU and scales with the length of the comic loaded. For some formats, this can generate extra CPU load as some pages are extracted twice (one pass to reach the last page you viewed, second pass to prepare the pages before that page).Īnd last but not least, YACReader will also create page thumbnails for the cover flow. YACReader will also extract or pre-render the whole comic you opened, starting from the last page you viewed. When you open a comic for the second time, it will try to open the last page you viewed, which can need more CPU, depending on the format used. When you open a comic for the first time, YACReader will extract or render its first page. This will naturally use more CPU than hardware rendering, nothing strange about that. When you disable the hardware acceleration you enable software rendering for the cover flow. System and versions: Manjaro Xfce 圆4 with latest updates Qt 5.12.3 with CONFIG+=no_pdf instead of CONFIG+=pdfium.ĮDIT: the same issue happens when compiling the develop branch in Qt Creator using the default poppler PDF backend. Tried QML debugging in Qt Creator, but it didn't work on my system for some reason. But the call stack didn't indicate a problem in any thread. I tried to debug the issue in Qt Creator by interrupting YACReader built in Debug mode while it was using the entire CPU core. This time the CPU usage will likely stay high, e.g. If the YACReader CPU usage goes down to 0-1% after a few seconds, exit YACReader and open the same comic again.A comic book never opened in YACReader before is preferable. Also seems to happen more often when opening by double-clicking in YACReaderLibrary. The bug happens more often for large comics (>=100 pages). Disable hardware acceleration in YACReader options.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |