-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid infinite digest loop caused by $watch and $timeout #10036
Merged
weltenwort
merged 1 commit into
elastic:master
from
weltenwort:fix-debounce-digest-loop
Jan 31, 2017
Merged
Avoid infinite digest loop caused by $watch and $timeout #10036
weltenwort
merged 1 commit into
elastic:master
from
weltenwort:fix-debounce-digest-loop
Jan 31, 2017
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
695b9c1
to
23471b2
Compare
jenkins, test this |
Test failure looked unrelated. Once they pass this LGTM. We should backport to 5.2 as well. |
Bargs
approved these changes
Jan 27, 2017
thanks, @Bargs. The failure seems to be related to the map tile changes. I'll rebase on master and try again. |
The custom debounce implementation uses Angular's `$timeout`, which interacts unfavourably with the unconditional `$watch` handler used in the `fixed-scroll` directive. It results in an infinite digest being triggered about every 100ms. To avoid that, this commit uses the `invokeApply` option of `$timeout` and instead calls `$scope.$apply` conditionally.
23471b2
to
13c677d
Compare
lukasolson
approved these changes
Jan 28, 2017
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
weltenwort
added a commit
that referenced
this pull request
Jan 31, 2017
Backports PR #10036 **Commit 1:** Avoid infinite digest loop in debounce The custom debounce implementation uses Angular's `$timeout`, which interacts unfavourably with the unconditional `$watch` handler used in the `fixed-scroll` directive. It results in an infinite digest being triggered about every 100ms. To avoid that, this commit uses the `invokeApply` option of `$timeout` and instead calls `$scope.$apply` conditionally. * Original sha: 13c677d * Authored by Felix Stürmer <stuermer@weltenwort.de> on 2017-01-24T11:30:41Z
weltenwort
pushed a commit
that referenced
this pull request
Jan 31, 2017
Backports PR #10036 **Commit 1:** Avoid infinite digest loop in debounce The custom debounce implementation uses Angular's `$timeout`, which interacts unfavourably with the unconditional `$watch` handler used in the `fixed-scroll` directive. It results in an infinite digest being triggered about every 100ms. To avoid that, this commit uses the `invokeApply` option of `$timeout` and instead calls `$scope.$apply` conditionally. * Original sha: 13c677d * Authored by Felix Stürmer <stuermer@weltenwort.de> on 2017-01-24T11:30:41Z
weltenwort
added a commit
that referenced
this pull request
Jan 31, 2017
Backports PR #10036 **Commit 1:** Avoid infinite digest loop in debounce The custom debounce implementation uses Angular's `$timeout`, which interacts unfavourably with the unconditional `$watch` handler used in the `fixed-scroll` directive. It results in an infinite digest being triggered about every 100ms. To avoid that, this commit uses the `invokeApply` option of `$timeout` and instead calls `$scope.$apply` conditionally. * Original sha: 13c677d * Authored by Felix Stürmer <stuermer@weltenwort.de> on 2017-01-24T11:30:41Z
weltenwort
pushed a commit
that referenced
this pull request
Jan 31, 2017
Backports PR #10036 **Commit 1:** Avoid infinite digest loop in debounce The custom debounce implementation uses Angular's `$timeout`, which interacts unfavourably with the unconditional `$watch` handler used in the `fixed-scroll` directive. It results in an infinite digest being triggered about every 100ms. To avoid that, this commit uses the `invokeApply` option of `$timeout` and instead calls `$scope.$apply` conditionally. * Original sha: 13c677d * Authored by Felix Stürmer <stuermer@weltenwort.de> on 2017-01-24T11:30:41Z
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#9326 introduced the usage of a custom
debounce
implementation in thefixed-scroll
directive used for the discover table. That customdebounce
implementation uses Angular's$timeout
, which interacts unfavourably with the unconditional$watch
handler used in thefixed-scroll
directive. It results in a digest being triggered about every 100ms, even when the page is otherwise idle:$watch
starts$timeout
$timeout
elapses, triggers a digestPreventing
debounce
from always triggering a digest cycle in combination with an explicit$apply
does not exhibit that behaviour:It also avoids some additional digest cycles when the scroll width has not changed.