Announcement

Collapse
No announcement yet.

Google Uncovers CPU Bug For Geminilake, Affecting At Least Firefox & Chrome

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

  • #31
    Originally posted by pal666 View Post
    l2 misses are affected by memory footprint, not by jit recompiling
    Yeah, and how do you think one gets such a large memory footprint of frequently-executed code?

    Most software spends the majority of its time in a few hot spots. Hence, not many ICache misses. However, with a bunch of tabs open, each running large amounts of spy-ware infested Javascript that the browser has dutifully transformed into native executable code, I would expect to see a much larger active footprint of code executing.

    Comment


    • #32
      Originally posted by pal666 View Post
      you guessed wrong
      You don't have enough information to say that! If it's a CPU bug, then the underlying trigger is not necessarily isolated along process or thread boundaries.

      Comment


      • #33
        Originally posted by carewolf View Post
        As usual you have no idea what you are talking about.
        No, pal666 is always right. If his statements don't comport with reality, then it must be a bug in reality.

        Comment


        • #34
          Originally posted by pal666 View Post
          jitted javascript probably runs in separate process anyway
          There's no way you could be more wrong. Main thread JavaScript (not a WebWorker) runs in a single thread along with things like layout and styles, rendering, and pretty much everything related to a given tab. There is a reason why bad scripts make websites run like garbage, and that's because they block the main thread.

          Comment

          Working...
          X