![]() Current Flash Player version: 23.0.0.207.Now in my Chrome, all flash contents will show a warning "Adobe Flash Player is out of date" (even if I disable Flash Player in chrome://plugins), and Chrome refused to play them. If, however, I do this: sudo ln -s /usr/lib/adobe-flashplugin/ /opt/google/chrome/PepperFlash # There's no PepperFlash folder by defaultīut chrome://plugins and chrome://version still show 23.0.0.185, and Flash contents still show the "out of date" warning and Chrome still refuse to play them. I've tried uninstalling and reinstalling Chrome with no avail. It seems this relates to how Google Chrome distribute Flash Player in version 54+, so I used the "Check for update" button in chrome://components, and it says Linking everything from /usr/lib/adobe-flashplugin/ to ~/.config/google-chrome/PepperFlash/ didn't seem to help. It seems Chrome insist on using proxy "DIRECT" when it checks for component update (. ![]() ![]() , see it in chrome://net-internals/#events), despite me setting PAC proxy in dconf and Chrome extension, so our lovely GFW happily blocked the request. Found a VPN and the component successfully upgraded.Since the beginning of Chrome, benchmarks have been a key way by which we drive performance optimizations that benefit users. The most relevant web benchmarks today are Speedometer, MotionMark, and Jetstream. Over the last year Chrome has invested in optimizing against these specific benchmarks and has just achieved our highest scores across all three. These gains were achieved through a combination of large projects and small improvements. Announcing our brand new mid-tier compiler: Maglev In today’s The Fast and the Curious post, we want to share just some of the ways we drove these improvements in Chrome. We’re bringing a new mid-tier compiler to Chrome. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |