1815791 - Avoid dispatching any action after the debugger starts being destroyed

Status: NEW

(DevTools :: Debugger, task, P3)

Description

[Alexandre Poirot [:ochameau]]

Some action are trying to bail out early in case the debugger starts destroying.
But it should rather be done at the framework level.
We should have a general mechanism that ensures that no action can be dispatches after we start destroying the panel.
AFAIK, there isn't anything in place which would stop dispatching action from async action being overlapping the panel's destruction.

Comment 1

[Alexandre Poirot [:ochameau]]

It looks like this easily happen on try, but not so easily manually.
And it looks like we would benefit from bug 1814607. These tests don't seem to wait correctly for reload's async actions.

Comment 2

[Alexandre Poirot [:ochameau]]

Attachment: Bug 1815791 - [devtools] Stop dispatching any action after debugger panel's destruction.