Project

General

Profile

Actions

Bug #44228

closed

mgr/dashboard: Error: ViewDestroyedError: Attempt to use a destroyed view: detectChanges

Added by Ernesto Puerta about 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
UI
Target version:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When logging out and then in (same user, for example, admin), browser (Chrome) throws the following error in the console:

Uncaught Error: Uncaught (in promise): Error: ViewDestroyedError: Attempt to use a destroyed view: detectChanges
Error: ViewDestroyedError: Attempt to use a destroyed view: detectChanges
    at viewDestroyedError (core.js:28818)
    at Object.debugUpdateDirectives [as updateDirectives] (core.js:45256)
    at checkAndUpdateView (core.js:44271)
    at callWithDebugContext (core.js:45632)
    at Object.debugCheckAndUpdateView [as checkAndUpdateView] (core.js:45194)
    at ViewRef_.detectChanges (core.js:31126)
    at notifications-sidebar.component.ts:102
    at ZoneDelegate.invoke (zone-evergreen.js:359)
    at Object.onInvoke (core.js:39699)
    at ZoneDelegate.invoke (zone-evergreen.js:358)
    at resolvePromise (zone-evergreen.js:797)
    at zone-evergreen.js:862
    at ZoneDelegate.invokeTask (zone-evergreen.js:391)
    at Object.onInvokeTask (core.js:39680)
    at ZoneDelegate.invokeTask (zone-evergreen.js:390)
    at Zone.runTask (zone-evergreen.js:168)
    at drainMicroTaskQueue (zone-evergreen.js:559)
    at ZoneTask.invokeTask [as invoke] (zone-evergreen.js:469)
    at invokeTask (zone-evergreen.js:1603)
    at XMLHttpRequest.globalZoneAwareCallback (zone-evergreen.js:1640)

This might be happening because of our using ngZone.runOutsideAngular (summaryService has weirdly diverged from what one would expect to be an API service). So if we don't want Angular to mess up our stuff for whatever (?) the reason, then I'm afraid we cannot go back and tell Angular 'hey, please detect my changes... exactly, the ones I didn't want you to know about'. Just a guess, but looks like that.


Related issues 1 (0 open1 closed)

Copied to Dashboard - Backport #44992: octopus: mgr/dashboard: Error: ViewDestroyedError: Attempt to use a destroyed view: detectChangesResolvedAlfonso MartínezActions
Actions

Also available in: Atom PDF