- #Set yacreader to run at startup pdf#
- #Set yacreader to run at startup software#
- #Set yacreader to run at startup code#
That means removing all the dead Qt2 and Qt3 codepaths, properly converting the Qt4 stuff to Qt5, converting the signal/slot connections to modern syntax to allow our compiler to check for connection errors and preferably getting rid of the whole thread and mutex mess, if possible. My gut tells me that there is another problem hiding somewhere, possibly related to our library database backend or the sync mechanism between reader and library, and I really don't like that.Īlso, if we're going to mess with the pictureflow code, we shouldn't just fix the obvious bugs but do some proper refactoring. Even if we fix the errors in pictureflow exposed by this bug this still does not explain why this is being triggered at all. What really bothers me (and too) is that the cpu bug seemingly only strikes when YACReader is being launched from QtCreator or YACReaderLibrary and the load of the comic was interrupted at least once.
#Set yacreader to run at startup code#
Well, we already knew that the pictureflow code isn't in the best shape. Older versions suffer from a bug where some of our third party code installed a global debug handler which ate all the output without displaying it. It works very well with files in the 10 to 100 mb range, but with gigabyte size comics it gets a little memory and cpu hungry.ītw, if you want to see debug output, the develop version of YACReaderLibrary has a command option to set a loglevel on launch. 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.
#Set yacreader to run at startup software#
When you disable the hardware acceleration you enable software rendering for the cover flow.
#Set yacreader to run at startup pdf#
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.
0 kommentar(er)
