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

app not being destroyed when destroying the platform (PlatformRef) #12015

Closed
talsi opened this issue Sep 30, 2016 · 1 comment
Closed

app not being destroyed when destroying the platform (PlatformRef) #12015

talsi opened this issue Sep 30, 2016 · 1 comment
Labels
area: core Issues related to the framework runtime freq1: low type: bug/fix

Comments

@talsi
Copy link

talsi commented Sep 30, 2016

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
modules are not being destroyed when destroying the platform (PlatformRef).

Expected behavior
bootstrapped app should be destroyed after the platform gets destroyed

Reproduction of the problem
plunker (BUG2 - README.md): http://plnkr.co/edit/1qK9m8WrkXejzoM20glQ?p=preview
git repo (BUG2 - README.md): https://github.com/talsi/ng2-bug-reproduce-destroy

  1. wait for angular app to load.
  2. click on button "destroy platform" (from destruction panel).
  3. optional - repeat step 2

What is the motivation / use case for changing the behavior?
PlatformRef.destroy definition is "Destroy the Angular platform and all Angular applications on the page.". I have several ng2 apps hosted in an exsiting single page application. i need to be able to bootsrap and destroy an app without having side effects.

Please tell us about your environment:

Windows10, WebStorm, NPM 3.10.3, NodeJs 6.5.0, Angular-CLI 1.0.0-beta.16

  • Angular version: 2.0.0

    "dependencies": {
    "@angular/common": "2.0.0",
    "@angular/compiler": "2.0.0",
    "@angular/core": "2.0.0",
    "@angular/forms": "2.0.0",
    "@angular/http": "2.0.0",
    "@angular/platform-browser": "2.0.0",
    "@angular/platform-browser-dynamic": "2.0.0",
    "@angular/router": "3.0.0",
    "core-js": "^2.4.1",
    "rxjs": "5.0.0-beta.12",
    "ts-helpers": "^1.1.1",
    "zone.js": "^0.6.23"
    },
    "devDependencies": {
    "@types/jasmine": "^2.2.30",
    "angular-cli": "1.0.0-beta.16",
    "codelyzer": "~0.0.26",
    "jasmine-core": "2.4.1",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "4.0.9",
    "ts-node": "1.2.1",
    "tslint": "3.13.0",
    "typescript": "2.0.2"
    }

  • Browser: Chrome 53.0.2785.116 m

  • Language: TypeScript 2.0.2

  • Node (for AoT issues): node --version = 6.5.0

@vicb vicb added type: bug/fix area: core Issues related to the framework runtime labels Oct 1, 2016
DzmitryShylovich pushed a commit to DzmitryShylovich/angular that referenced this issue Jan 1, 2017
DzmitryShylovich pushed a commit to DzmitryShylovich/angular that referenced this issue Jan 1, 2017
DzmitryShylovich pushed a commit to DzmitryShylovich/angular that referenced this issue Jan 1, 2017
DzmitryShylovich pushed a commit to DzmitryShylovich/angular that referenced this issue Jan 1, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: core Issues related to the framework runtime freq1: low type: bug/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants