This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 973
Ledger getPublisher perf is bad even if ledger is off #10186
Milestone
Comments
35 tasks
@NejcZdovc volunteered for this |
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Jul 28, 2017
Resolves brave#10186 Auditors: @bbondy Test Plan: - run a profiler and check that ledger is not called when hovering over links or typing in find bar
8 tasks
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Jul 29, 2017
Resolves brave#10186 Auditors: @bbondy Test Plan: - run a profiler and check that ledger is not called when hovering over links or typing in find bar
bbondy
added a commit
that referenced
this issue
Aug 1, 2017
Removes unnecessary setFocusedFrame calls
bbondy
added a commit
that referenced
this issue
Aug 1, 2017
Removes unnecessary setFocusedFrame calls
bbondy
added a commit
that referenced
this issue
Aug 1, 2017
Removes unnecessary setFocusedFrame calls
bbondy
added a commit
that referenced
this issue
Aug 1, 2017
Removes unnecessary setFocusedFrame calls
This was referenced Aug 7, 2017
This was referenced Aug 9, 2017
This was referenced Aug 11, 2017
This was referenced Aug 16, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#10192 (comment)
All typing and mouse movement call into getPublisher which can be expensive.
See also: #9311
I think mainly the problem is when publisher info isn't found it keeps looking for it. We could store that it was looked up but not found and then not re-lookup in that case. But also I think it's not needed to be even called into for cases like mouse move and key down.
The text was updated successfully, but these errors were encountered: