![]() 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.HTTPS is here to stay and we need to get used to using it properly - and not bypassing the warnings with a hack that is liable to change and doesn't work the same as a full HTTPS solution. Caching for example is completely ignored for untrusted certificates. If you leave the certificate untrusted then certain things do not work. If you are using this when using a self-signed certificate for local testing then why not just add your self-signed certificate certificate to your computer's certificate store so you get a green padlock and do not have to type this? Note Chrome insists on a SAN field in certificates now so if just using the old subject field then even adding it to the certificate store will not result in a green padlock. It would not surprise me if they removed it completely in future. I think the message from the Chrome team is clear - you should not use it. Rotate the keyword to help prevent misuse. The security interstitial bypass keyword hasn't changed in two yearsĪnd awareness of the bypass has been increased in blogs and social ![]() The last time they changed they put this comment in the commit: As Steffen pointed out in the comments below, it is available in the code should it change again though they now base64 encode it to make it more obscure. They changed it recently from badidea to thisisunsafe so everyone using badidea, suddenly stopped being able to use it. The chrome developers also do change this periodically. The fact it's needed suggests there is something wrong with the https connection - like the site or your connection to it has been hacked. ![]() ![]() HSTS specifically adds protections for bad certs to prevent you clicking through them. You should find out why the site is showing the error and/or stop using it until they fix it. Needless to say use of this "feature" is a bad idea and is unsafe - hence the name. ![]() It is also remembered for that site and you have to click on the padlock to reset it (so you can type it again): So if you type that once, you will only get through that site and all other sites will need a similar type-through. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |