Skip to content
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

fix(): SSR memory leaks #2294

Merged
merged 4 commits into from
Jan 21, 2020
Merged

fix(): SSR memory leaks #2294

merged 4 commits into from
Jan 21, 2020

Conversation

jamesdaniels
Copy link
Member

Checklist

  • Issue number for this PR: #nnn (required)
  • Docs included?: (yes/no; required for all API/functional changes)
  • Test units included?: (yes/no; required)
  • In a clean directory, yarn install, yarn test run successfully? (yes/no; required)

Description

Code sample

Valentin Funk and others added 4 commits January 21, 2020 11:34
* chore: allow passsing Scheduler to fromRef

This follows a convention from RxJS where observable creators allow passing a scheduler (e.g. fromPromise, of, empty, ...)

Setting the default scheduler to asyncScheduler has the same effect as the delay(0) which is why it was removed.

* fix: fix memory leak in SSR

* fix(universal-test): bring back universal-test app

* fix: use macrotask

* fix: schedule completed and error notifications in the specified scheduler

And add tests to verify behavior

* chore: update misleading comment

* fix(typings): don't type ZoneScheduler.delegate to support old TS versions

* fix(keepUnstableUntilFirst): multicast only after rescheduling

BREAKING: fromRef() observables are no longer multicasted by default

* fix(keepUnstableUntilFirst): schedule emissions inside of angular synchronously, invoke zone task if unsubscribed before first emission

Co-authored-by: James Daniels <james@jamesdaniels.net>
@googlebot

This comment has been minimized.

1 similar comment
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@jamesdaniels
Copy link
Member Author

FYI wrapping this up here @kamshak. Will merge today and cut in the next release. Thanks for your hard work here!

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

1 similar comment
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@jamesdaniels jamesdaniels merged commit 25e5b04 into master Jan 21, 2020
@jamesdaniels jamesdaniels deleted the ssr_working branch January 21, 2020 20:39
jamesdaniels added a commit that referenced this pull request Feb 2, 2020
Co-authored-by: Valentin Funk <funk.valentin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants