Announcement

Collapse
No announcement yet.

Google Chrome 57 Enters Beta

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Google Chrome 57 Enters Beta

    Phoronix: Google Chrome 57 Enters Beta

    Fresh off last week's release of Chrome 56 with WebGL 2.0 by default, FLAC audio support, and more, is now the Chrome 57 beta...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Which was the Chrome version that took away your ability to disable EME?

    Comment


    • #3
      There was talk about reducing memory consumption past Chrome 55. Anyone knows how that is going? I don't use Chrome on a regular basis, so I really couldn't tell.

      Comment


      • #4
        So there is a new feature coming that is supposed to stop advertisers from misbehaving, it is basically iframes cannot change the URL unless there has been user interaction with it.

        sounds good in theory, but lots of drop in payment gateways use iframes for PCI compliance - so it should be fun to see how those use cases are addressed.

        Comment


        • #5
          This issue came up on Slashdot some days ago and IMO deserves much more attention that it is currently getting. Maybe we are just exhausted with that other new circus in town.

          An anonymous reader shares a Ghacks report: Google made a change in Chrome 57 that removes options from the browser to manage plugins such as Google Widevine, Adobe Flash, or the Chrome PDF Viewer. If you load chrome://plugins in Chrome 56 or earlier, a list of installed plugins is displayed to you....

          Comment


          • #6
            Originally posted by ldo17 View Post
            Which was the Chrome version that took away your ability to disable EME?
            is this one, chrome 57

            Comment


            • #7
              Originally posted by boxie View Post
              So there is a new feature coming that is supposed to stop advertisers from misbehaving, it is basically iframes cannot change the URL unless there has been user interaction with it.

              sounds good in theory, but lots of drop in payment gateways use iframes for PCI compliance - so it should be fun to see how those use cases are addressed.
              Another cool thing you can do with iframe is to add the "sandbox" attribute. Example <iframe src="..." sandbox />, then you can prevent the iframe from executing JavaScript or other such stuff.

              Last edited by uid313; 03 February 2017, 05:21 AM. Reason: https://msdn.microsoft.com/en-us/hh563496

              Comment


              • #8
                Originally posted by misGnomer View Post
                This issue came up on Slashdot some days ago and IMO deserves much more attention that it is currently getting. Maybe we are just exhausted with that other new circus in town.

                An anonymous reader shares a Ghacks report: Google made a change in Chrome 57 that removes options from the browser to manage plugins such as Google Widevine, Adobe Flash, or the Chrome PDF Viewer. If you load chrome://plugins in Chrome 56 or earlier, a list of installed plugins is displayed to you....
                One more reason to stick with Seamonkey/Firefox.
                On the other hand, if the above was modified in Chromium, it will also trickle down into Vivaldi at some point

                Comment


                • #9
                  Originally posted by bug77 View Post
                  There was talk about reducing memory consumption past Chrome 55. Anyone knows how that is going? I don't use Chrome on a regular basis, so I really couldn't tell.
                  You're probably thinking about "Project TRIM". Here's slides regarding that from this week's BlinkOn. https://docs.google.com/presentation...144f3402ef_0_0

                  Here's the Project TRIM mailing list https://groups.google.com/a/chromium...m/project-trim

                  Basically they've done many significant reductions and have been focused on tooling required to understand memory usage better. There's been things like removing duplicated encoded images from memory, removing lots of stuff like this https://groups.google.com/a/chromium...im/1OfAa01uOa8 , implementing a heap compaction feature for Blink's Garbage Collector (Oilpan), this was actually done by an Opera employee: https://codereview.chromium.org/2531973002/ .

                  But so far the biggest consumer of memory left (as noted in the slides I linked before) remains JavaScript source strings, that are required by the current JavaScript-engine. Once the move to TurboFan & Ignition is made, the JS engine just consumes bytecode and no longer needs access to the source strings, allowing to drop them from the memory completely, which should be a big win.

                  Feel free to ask any questions that come to mind regarding Chromium / it's subsystems, I can answer probably :P

                  Comment


                  • #10
                    Originally posted by FishPls View Post

                    You're probably thinking about "Project TRIM". Here's slides regarding that from this week's BlinkOn. https://docs.google.com/presentation...144f3402ef_0_0

                    Here's the Project TRIM mailing list https://groups.google.com/a/chromium...m/project-trim

                    Basically they've done many significant reductions and have been focused on tooling required to understand memory usage better. There's been things like removing duplicated encoded images from memory, removing lots of stuff like this https://groups.google.com/a/chromium...im/1OfAa01uOa8 , implementing a heap compaction feature for Blink's Garbage Collector (Oilpan), this was actually done by an Opera employee: https://codereview.chromium.org/2531973002/ .

                    But so far the biggest consumer of memory left (as noted in the slides I linked before) remains JavaScript source strings, that are required by the current JavaScript-engine. Once the move to TurboFan &amp; Ignition is made, the JS engine just consumes bytecode and no longer needs access to the source strings, allowing to drop them from the memory completely, which should be a big win.

                    Feel free to ask any questions that come to mind regarding Chromium / it's subsystems, I can answer probably :P
                    Thanks for the reply.

                    I don't have specific questions because I don't really use Chrome (because it's a memory hog and because it keeps nagging me about logging into my Google account). But I keep my eyes on it, because from time to time I get to recommend people one browser or another.

                    Comment

                    Working...
                    X