Memory Leak Warning in Firefox

[darkwing]

Describe the bug
I see the following error in the Firefox console when developing the MetaMask extension:

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in ConfirmTransactionBase (created by ConnectFunction)
    in ConnectFunction (created by Context.Consumer)
    in withRouter(Connect(ConfirmTransactionBase)) (created by ConfirmSendEther)
    in ConfirmSendEther (created by ConnectFunction)
    in ConnectFunction (created by Context.Consumer)
    in withRouter(Connect(ConfirmSendEther)) (created by Context.Consumer)
    in Route (created by ConfirmTransaction)
    in Switch (created by ConfirmTransaction) backend.js:32
    n backend.js:32
    instrumentConsole instrument.js:104
    React 5
    handleSubmit confirm-transaction-base.component.js:502
    (Async: promise callback)
    handleSubmit confirm-transaction-base.component.js:500
    (Async: promise callback)
    handleSubmit confirm-transaction-base.component.js:489
    React 6
    sentryWrapped helpers.js:74
    React 3
    unstable_runWithPriority scheduler.development.js:697
    React 5
    unstable_runWithPriority scheduler.development.js:697
    React 6
    sentryWrapped helpers.js:74
    (Async: EventListener.handleEvent)
    _wrapEventTarget trycatch.js:75

To Reproduce (REQUIRED)
Unfortunately no concrete steps to reproduce. Best detail I can give is that I've been bringing up the Swap and Send screens

Screenshots

Browser details (please complete the following information):

• OS: OS X
• Hardware Wallet: None
• Browser: Firefox Nightly 83
• MetaMask Version: 8

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.