New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 872930 link

Starred by 1 user
Status: Fixed
Owner:
brucedaw...@chromium.org
Closed: Oct 4
Cc:
█ krajshree@chromium.org
oysteine@chromium.org
bokan@chromium.org
chrome-perf-bugs@google.com
Components:
EstimatedDays: ----
NextAction: 2018-09-17
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Performance issue + Can't capture trace

Reported by gleis_be...@hotmail.com, Aug 9 
Chrome Version       :Version 68.0.3440.106 (Official Build) (64-bit)
Operating System and Version: WIN 10 HOME ED.
URLs (if applicable) :  N/A

Description of performance problem:
laptop touchpad will not scroll anymore. Has never been a problem until lately. Unable to recall what I did to break it. Touchpad works in ALL other browsers, apps and explorer windows. Will not scroll in Chrome [any version], Canary or any portable versions.


Remember to attach your trace file to this bug!:

I followed instructions, clicked 'record' and tried to scroll on same page. Rather than a report, I received the following error dialogue...
I repeated steps but tried to scroll in a different tab. I got a second error 
  ""...
Error
✕
While importing:
Error: Incompatible Thread event version.
    at ThreadParser.decodeCSwitchFields (chrome://tracing/tracing.js:4497:259)
    at ThreadParser.decodeCSwitch (chrome://tracing/tracing.js:4498:1378)
    at EtwImporter.parseEvent (chrome://tracing/tracing.js:4515:304)
    at Array.forEach (<anonymous>)
    at EtwImporter.importEvents (chrome://tracing/tracing.js:4512:22)
    at importer (chrome://tracing/tracing.js:1293:232)
    at task.subTask (chrome://tracing/tracing.js:1289:268)
    at Task.run (chrome://tracing/tracing.js:2199:95)
    at runAnother (chrome://tracing/tracing.js:2202:371)
    at runTask (chrome://tracing/tracing.js:2178:57)

and again...
Error
✕
While importing:
Error: Incompatible Thread event version.
    at ThreadParser.decodeCSwitchFields (chrome://tracing/tracing.js:4497:259)
    at ThreadParser.decodeCSwitch (chrome://tracing/tracing.js:4498:1378)
    at EtwImporter.parseEvent (chrome://tracing/tracing.js:4515:304)
    at Array.forEach (<anonymous>)
    at EtwImporter.importEvents (chrome://tracing/tracing.js:4512:22)
    at importer (chrome://tracing/tracing.js:1293:232)
    at task.subTask (chrome://tracing/tracing.js:1289:268)
    at Task.run (chrome://tracing/tracing.js:2199:95)
    at runAnother (chrome://tracing/tracing.js:2202:371)
    at runTask (chrome://tracing/tracing.js:2178:57)

Comment 1 by vamshi.kommuri@chromium.org, Aug 10

Labels: Needs-Triage-M68

Comment 2 by krajshree@chromium.org, Aug 10

Cc: krajshree@chromium.org
Components: Blink>JavaScript>GC
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome reported version #68.0.3440.106 and latest canary #70.0.3517.0.

Following are the steps followed to reproduce the issue.
------------
1. Opened crbug.com on chrome browser.
2. Scrolled using laptop touchpad.
3. Observed that the page scrolled without any issues.

reporter@ - Could you please check the issue on latest canary #70.0.3517.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Comment 3 by hablich@chromium.org, Aug 10

Components: -Blink>JavaScript>GC Blink
does not look related to V8.

Comment 4 by e...@chromium.org, Aug 16

Components: -Blink Blink>Input

Comment 5 by bokan@chromium.org, Aug 17

Cc: -rsch...@chromium.org bokan@chromium.org
Components: Speed>Tracing
Labels: OS-Windows
gleis_berry@: Does the error on tracing occur in Stable? All versions of Chrome?

Adding Speed>Tracing. Are we aware of any issues that would prevent a trace from being captured with the error and stack provided?

Comment 6 by bokan@chromium.org, Aug 17

Summary: Performance issue + Can't capture trace (was: Performance issue:)

Comment 7 by bokan@chromium.org, Aug 23

Components: -Blink>Input
Ping

Comment 8 by bokan@chromium.org, Aug 23

NextAction: 2018-08-30

Comment 9 by monor...@bugs.chromium.org, Aug 30 

The NextAction date has arrived: 2018-08-30

Comment 10 by bokan@chromium.org, Aug 30

Cc: oysteine@chromium.org
+oysteine@ - do you know why the user might be getting the errors when capturing a trace?

Comment 11 by brucedaw...@chromium.org, Sep 10 

ThreadParser.decodeCSwitchFields is used for decoding ETW context switch data. This data is only recorded if "System tracing" is enabled in the chrome://tracing configuration options and if Chrome is running as administrator. We don't really recommend running Chrome as an administrator because it can be a security risk, but if that is necessary for some reason then just un-check System Tracing.

I have a change to decodeCSwitchFields() which will display the header version data when it hits this error. This shows that on my machine the header version is 4, which means that the catapult code needs to be updated. I filed https://github.com/catapult-project/catapult/issues/4582.

In the meantime, could the original filer of this bug please try again to get a trace with "System tracing" disabled, or with Chrome running as non-admin?

Comment 12 by bokan@chromium.org, Sep 11

NextAction: 2018-09-17
Thanks for the explanation!

Comment 13 by brucedaw...@chromium.org, Sep 12 

The thread event version bug has been fixed and should show up in a canary build soon - tomorrow probably. But, disabling "System tracing" is the simplest way to avoid the issue and be able to record a trace.

https://chromium-review.googlesource.com/c/catapult/+/1217454

Comment 14 by brucedaw...@chromium.org, Sep 14 

There was a slight delay due to the need to roll catapult DEPS but the fix has made it to canary - 71.0.3552.2. I just successfully recorded a system trace with context switches from chrome canary running as administrator.

For other versions of Chrome the recommended solution to allowing tracing to succeed is to disable "System tracing".

Comment 15 by monor...@bugs.chromium.org, Sep 17 

The NextAction date has arrived: 2018-09-17

Comment 16 by brucedaw...@chromium.org, Oct 4

Owner: brucedaw...@chromium.org
Status: Fixed (was: Unconfirmed)
The inability to record traces has been fixed (in canary anyway) and a workaround provided for all other channels (disable "System tracing"). The performance issue was never described so that's a no-repro, but I'm closing this as fixed due to the tracing fix.
►

Sign in to add a comment