What happens if you run glxgears?  Does the same system lag occur?  If so, this is probably a bug in your graphics drivers and not Chromium.

 thomasanderson@chromium.org GLXGears are completely fine, games run smooth and without problems as well. Only a couple of them cause a little bit of slowdown, bot only chrome manages to make using system a nightmare.

Unable to reproduce this issue on reported version 63.0.3239.132 on chromium using Ubuntu 14.04,i5-3570,Mesa driver. Enabled hardware acceleration -- No lag is seen; On Disabling and playing video -- No tear is seen.

This might be specific to Arch Linux64 which is not available with ET/Inhouse team. Could someone from MTV please have a look at this issue.

Also this looks similar to  issue 788510 . cc'ing @ danakj from 788510. Could you please have a look at this.

Thanks!

fyi a similar-sounding tearing issue was recently fixed at  bug 344141 

Re: tearing: in software mode, Chrome doesn't synchronize to vsync. If you have a compositing manager, that is what should take care of vsync / tear avoidance.

Re: system jank: can you run 'nvidia-smi -q' and attach the output?

 sc00335...@techmahindra.com you used Mesa. Try Using Nvidia properiary driver.

Thank you for providing more feedback. Adding requester "piman@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Still needs feedback wrt output of 'nvidia-smi -q' from someone who reproduces the jank / lag.

Here is my output of 'nvidia-smi -q' it may help you

https://drive.google.com/open?id=1MDnnBju66IXJi1JT4SBSXQXh8DEWZlOp

Thank you for providing more feedback. Adding requester "piman@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@#11: Is that output while the system experiences jank?
I was looking something along the lines of crbug.com/623786 but in your output very little GPU memory is used.

 piman@chromium.org that one was done without chrome/chromium running, here is a one with system being messed up by chrome:

https://drive.google.com/open?id=1aCptgTih_H1Qcm1-KBZme_fRsN1kTXdM

Thank you for providing more feedback. Adding requester "piman@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@#15: Nothing obviously wrong, so I don't really know.
I noticed that you have 2 X servers running, although not wrong per se, that's certainly somewhat unusual, maybe there is a bad interaction with that, and/or some other app running (I see Discord in the client list, which I believe is an app based on electron/chromium, so maybe there is some fighting going on there).

 piman@chromium.org but firefox has no problem at all with anything. So why i chrome so iffy ?

@#18 - I don't have any idea about the cause. Very likely Chrome uses X or the GPU in ways that are very different from Firefox. Maybe it tickles it in the wrong way. Maybe it runs into a bug.

piman@chromium.org i checked if Discord os coloding with Chrome, it doesnt.

Can i expect this bug to be fixed in next release of Chrome/Chromium ?

@#20: unlikely we can fix it in any way (let alone next release) until we understand the root cause of the bug and see if there are workarounds we can do. At this point all we can hope for is to make progress on that.

Does it still repro if running with only 1 X server?

 piman@chromium.org killing either one logs me out.

I'm not sure how to move this further at this point. Leaving Available for now.

piman@chromium.org i can record it if it will help by any chance

I'm also experiencing lockups:

- core2 laptop running ubuntu 14.04.3
- nvidia 110m - driver 304.135
- chrome 64.0.3282.167
- all extensions removed
- dual monitor configuration

Easily reproducible with a single gmail tab open and gpu enabled in settings. When it occurs, I notice (with htop running) repeated startups of a chrome process with the commandline '-utility'. This utility process runs for about 1 second, quits then starts again in about 1 second, rinse, repeat.

Attached is a 4 second trace (from chrome://tracing) of the 'disabled by default' categories (which appears to record gpu usage). The spurious chrome process was started and shutdown twice during the logging.

When gpu is disabled there are no lags and htop does not show any spuriously created chrome processes.

Let me know if you need more info or specific logs.

Cheers

Sorry I don't mean to troll anyone but I just noticed that my log has six b64 encoded screenshots... anyway to disable those from the tracedump?

Attached is a 4 second trace (from chrome://tracing) of the 'disabled by default' categories (which appears to record gpu usage). The spurious chrome process was started and shutdown twice during the logging.

Deleted: trace_lockups-nvidia-110m.json.gz 3.9 MB

trace_lockups-nvidia-110m.json.gz 3.9 MB Download

Ya, that looks like a 12 second trace I gave you there. The spurious process did only start twice, so I guess it was more of a 3 sec on and 3 sec off sort of deal. For those 12 seconds I was leaving the machine to just record - I was not trying to test any lagginess. Let me know if you want any specific user interaction while recording.

I noticed that if i use no sandbox flag it fixed it for 10seconds... I dont know why