Chrome has become extremely laggy - Did the update break?

  • in the game im currently working on the debugger/profile says draw call: 0.6-1.1 events: ~0.5, but the fps is dropped to ~50 and the game is laggy

    while in firefox its constant 60 fps, normally it was the other way around, chrome always performed better for me while firefox most times had some glitches and lag

    Ashley spaceblaster test gets a score of 60 on firefrox here und 58 on chrome, that means it runs smooth but not as good as in firefox while my firefox always was a bit laggyer then chrome, especially when much stuff happens like in this test

  • To be fair, Space Blaster probably isn't a good benchmark on PC's anymore - absolutely anything should be able to run that fine. This problem only effects my performance intensive stuff.

  • My game has a smattering of physics objects rather than just a few basic sprites, and I agree that space blaster is a bit basic for systems testing. Interestingly in the debugger, when I change from Inspect to the Profile screen in Chrome, the fps marches up (from 30 to 50) and CPU use goes right down (50% to 15%). The layout doesn't have that many objects on it (170) and my laptop is super-powerful with an embarrassingly high spec. Meanwhile, in both Firefox and IE11, the same game plays in the debugger at a solid 60 fps with 12% cpu.

  • thats because the inspect mode itself is very resource intensive

  • fldr - of course, I just thought it was interesting because it seems so much more resource intensive in Chrome compared with the other two browsers.

  • oh sorry i misunderstood you!

  • No worries!

  • My game has a smattering of physics objects rather than just a few basic sprites, and I agree that space blaster is a bit basic for systems testing. Interestingly in the debugger, when I change from Inspect to the Profile screen in Chrome, the fps marches up (from 30 to 50) and CPU use goes right down (50% to 15%). The layout doesn't have that many objects on it (170) and my laptop is super-powerful with an embarrassingly high spec. Meanwhile, in both Firefox and IE11, the same game plays in the debugger at a solid 60 fps with 12% cpu.

    The Debugger mode in Chrome has always been much more intensive, my game in debugger mode stutters, but in profile mode watching all the important metrics, its smooth 60 fps and 10-20% CPU used on my i5-3570K.

    Im still using Chrome 34 or so, haven't bothered to update.

  • This problem still occurs, and occurs just as badly in a layout with basically nothing going on.

    The C2 profiler didn't show anything up. Here's Chrome's CPU profile. I don't know how to interpret this - Could Ashley or someone else take a look at it?

  • Same problem here, im with the latest version of chrome and while testing my game it dropped like 6~8 FPS from previous chrome version... If I preview my game with Node-webkit it runs at solid 60fps

  • I actually posted in the forum some time back with the same issue and noticed the same drop in fps&cpu in debugger mode and the back to normalcy of 60fps in profile mode.

    <<link to forum post

    I have a feeling it's the combination of an updated chrome and C2. I think you should not judge the performance of your game based on the debugger view. I always switch to profile view after doing changes in debugger view.

    But still the issue is annoying , especially since it wasn't ever an issue before.

  • Pandy this has nothing to do with the debugger at all. The debugger has been a huge drain on performance since it was introduced, nothing's changed in that regard.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • sqiddster

    Sorry i used the wrong words. I meant in 'inspect' view. The drop in fps is only in the 'inspect' view, whereas the fps&cpu goes back to normal in the other views, i.e 'watch' and 'profile' view

    Now i'm aware of the drain, but it has gotten worse. I remember when i worked on my first project, and i used to get low fps, so i had to learn a lot and modify events and finally was able to get a stable 58-60 fps on my project in the 'inspect' view.

    fast forward a couple of months, i also started encountering lag as op when i previewed another project i was working on.So i previewed my first project which i had gotten 58-60 fps before, and i find that it's not giving 35-40 fps in 'inspect' view. But like others in this post, goes back to the normal 60fps in the other views(As opposed to before where i got 60fps in all views).

    I'm not techy so i'm not ready to point fingers, but i'm certain that something has changed somewhere to negatively affect C2.

  • Because of this thread I went and looked at my Chrome version...when I did that Chrome auto downloaded the newest version and my FPS immediately dropped from a constant 60 FPS which it has been for months down to around 47-55 and never hits 60 any more... now I have switched to IE for my previews.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)