New issue
Advanced search Search tips

Issue 760233 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Import Warning: UserModelBuilder: Please file a bug with this trace

Reported by delvarwo...@gmail.com, Aug 29 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
Import Warning: UserModelBuilder: Please file a bug with this trace: double-handled event: MouseLeave @ 4682.380999922752
▸ Interactions
CPU usage
Browser (pid 72350), uptime:161360s
FrameTreeNode
▸ NetLog
Chrome_CacheThread
Chrome_FileThread
DataManager:Request
▸ NetLog
▾ Chrome_IOThread
Chrome_PasswordStore_Thread
Chrome_ProcessLauncherThread
▸ DisplayScheduler:pending_swaps
InputLatency::Char
InputLatency::KeyUp
InputLatency::MouseDown
InputLatency::MouseLeave
▸ InputLatency::MouseMove
InputLatency::MouseUp
InputLatency::RawKeyDown
RenderWidgetHostImpl::repaint_ack_pending_
Scheduler:pending_submit_frames
SingleThreadProxy::SetDeferCommits
TimeoutMonitor
▾ CrBrowserMain
▾ LevelDBEnv
▾ TaskSchedulerForegroundBlockingWorker3
▾ TaskSchedulerForegroundWorker5
200843
Renderer (pid 2578), uptime:57s
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72360), uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72362), uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72363), uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72364), uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72365), uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72366), uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 72367): -, uptime:161359s
Renderer (pid 2159): 9psRBti.png (1414×276), uptime:2024s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
Renderer (pid 2576): chrome://tracing, uptime:57s
Renderer (pid 2585): Play! - Charisma The Chameleon, uptime:50s
RenderFrame
TopLevel
advanceLevelReducer
buttonAnimationReducer
ctaFormBlockerReducer
cutsceneReducer
debugReducer
defaultCameraReducer
doorsReducer
entityInteractionReducer
gameScreenReducer
kenBoinzReducer
keypressBlockerReducer
mapEntityPositionsFromPhysicsReducer
openMenuKeypressReducer
outOfBoundsReducer
parrotAnimationReducer
pathsReducer
physicsReducer
playerAnimationReducer
playerContactReducer
playerPositionReducer
playerScaleReducer
rAF
▾ RendererSchedulerIdlePeriod
screenAnimationReducer
segmentedEmitterReducer
speechReducer
teleportersReducer
translateEntityReducer
zoomReducer
▾ CrRendererMain
▾ Chrome_ChildIOThread
jitter
LayerTreeHostImpl::SetVisible
PendingTree:waiting
▸ ScheduledTasks
Scheduler:pending_submit_frames
▾ Compositor
▾ CompositorTileWorker1/18691
▾ CompositorTileWorker2/19203
▾ GpuMemoryThread
▾ TaskSchedulerRendererForegroundWorker0
▾ TaskSchedulerRendererForegroundWorker1
▾ TaskSchedulerRendererForegroundWorker2
Renderer (pid 2117): uBlock Origin, uptime:2079s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
▾ 32771
Renderer (pid 72361): uBlock Origin, uptime:161359s
RenderFrame
TopLevel
▾ CrRendererMain
▾ Chrome_ChildIOThread
▾ 32003
GPU Process (pid 72355), uptime:161360s
▾ Chrome_ChildIOThread
▾ CrGpuMain
Watchdog

What is the expected behavior?

What went wrong?
Debugging a webgl game in chrome, got this warning.

Did this work before? N/A 

Chrome version: 60.0.3112.101  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
trace_game-debug-trace.json.gz
4.8 MB Download

Comment 1 by rsesek@chromium.org, Aug 30 2017

Components: Speed>Tracing
Owner: benjhayden@chromium.org
Status: Assigned (was: Unconfirmed)
Status: Fixed (was: Assigned)
Thanks!
Is this actually breaking or blocking something in particular?
If so, let me know what and we can dig in.
Otherwise, I've already hidden these warnings to stop spamming. https://github.com/catapult-project/catapult/issues/3788
I'm going to assume that this is not breaking anything in particular; feel free to reopen if that is not the case.

Sign in to add a comment