![]() ![]() 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. 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. 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.Link to this close( conn(), query(), opts :: Keyword. Queries can be encoded and decoded without blocking the connection or pool. The DBConnection.Query protocol provide utility functions so that Lost when a connection disconnects but the process is reused. (configurable) exponential random backoff to reconnect. Should the connection be lost, attempts will be made to reconnect with Ping all stale connections which can then ping the database to keep If no requests are received for an idle interval, the pool will ![]() This prevents requestsīuilding up when the database can not keep up. Timeout and its request will be cancelled. If a calling process waits too long to start its request it will If a request or series of requests takes too long to handle in theĬlient process a timeout will trigger and the socket can be cleanly Remain responsive to OTP messages and can enqueue and cancel queued Simple blocking fashion, while the connection process itself will This is useful when the dataįor a request is large and means that a calling process can interactĪ side effect of this is that query handling can be written in a SomeĬallbacks will be called in the calling process, with the stateĬopied to and from the calling process. Settings View Source DBConnection behaviour (db_connection v2.4.3)Ī behaviour module for implementing efficient database connectionĬlient processes, pools and transactions.ĭBConnection handles callbacks differently to most behaviours. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |