Timeout instance still running after the host component is destroyed

[sulha199]

Timeout instance still running after the host component is destroyed. This happens on the build version generated by ng build.

Error: ViewDestroyedError: Attempt to use a destroyed view: detectChanges
    at viewDestroyedError (core.js:17883)
    at Object.debugUpdateDirectives [as updateDirectives] (core.js:28142)
    at checkAndUpdateView (core.js:27541)
    at callWithDebugContext (core.js:28411)
    at Object.debugCheckAndUpdateView [as checkAndUpdateView] (core.js:28113)
    at ViewRef_.push../node_modules/@angular/core/fesm5/core.js.ViewRef_.detectChanges (core.js:18930)
    at PopperController.push../node_modules/ngx-popper/fesm5/ngx-popper.js.PopperController.applyChanges (ngx-popper.js:645)
    at ngx-popper.js:623
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)
    at Object.onInvokeTask (core.js:24340)

Show timeout still running and then create another hidetimeout after host component is destroyed.

push../node_modules/ngx-popper/fesm5/ngx-popper.js.PopperController.scheduledHide | @ | ngx-popper.js:614
-- | -- | --
  | push../node_modules/ngx-popper/fesm5/ngx-popper.js.PopperController.show | @ | ngx-popper.js:546
  ...
  | push../node_modules/ngx-popper/fesm5/ngx-popper.js.PopperController.scheduledShow | @ | ngx-popper.js:591