[Sentry] [Bug]: Metamask fails to load if no response from RPC

[JABirchall]

Describe the bug

Metamask extention doesnt load, console errors log no response from RPC.

Steps to reproduce

I dunno

Error messages or log output

Setting up Sentry Remote Error Reporting for 'production': SENTRY_DSN sentry-install.js:1:1041
Removing intrinsics.Object.hasOwn sentry-install.js:1:102934
Content Security Policy: The page's settings blocked the loading of a resource at eval ("script-src"). moz-extension:9430:29
Content Security Policy: The page's settings blocked the loading of a resource at eval ("script-src"). moz-extension:4421:4
undefined sentry-install.js:1:102934
    h moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    (Async: setTimeout handler)
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    newValue moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10535
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    get moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    internalRequire moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10966
    runModule moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11357
    entryExports moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11347
    loadBundle moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11346
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
Uncaught (in promise) Error: No response from RPC
runtime-lavamoat.js:8939:17
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    InterpretGeneratorResume self-hosted:1458
    AsyncFunctionNext self-hosted:668
    (Async: async)
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    (Async: setTimeout handler)
    a moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/sentry-install.js:1
    apply self-hosted:2705
    newValue moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10535
    send moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    get moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-3.js:26
    default moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-6.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    g moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    AsyncFunctionNext self-hosted:668
    (Async: async)
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1
    internalRequire moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:10966
    runModule moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11357
    entryExports moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11347
    map self-hosted:180
    loadBundle moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/runtime-lavamoat.js:11346
    <anonymous> moz-extension://e6834f0f-3a74-4f6a-ad7f-cf3a09d748b9/ui-9.js:1

​

Version

10.18.3

Build type

No response

Browser

Firefox

Operating system

Windows

Hardware wallet

No response

Additional context

I shouldn't be effectivly locked out of my wallet if the RPC is down, I can't even change the RPC now.

[JABirchall]

Screenshot for context

[JABirchall]

Ive had to completly remove metamask and reinstall it again to be able to change RPC.

The and orginal RPC wasnt even down, it was working fine. dont know why metamask giving error the rpc was not responding.

[bschorchit]

Possibly related to #9196

[cinjon]

I'm running into this as well when testing with wdio. Sometimes it will work, most of the time I get the following error as shown in the screenshot.

This is on Chrome 104.0.5112.101 and Metamask 10.18.3.

.

[cinjon]

What is metamask using to do automated web integration tests? I have a reasonably small wdio setup that fails ~80% of the time due to this issue. (cc @bschorchit)

[cinjon]

@JABirchall Any chance you figured this out?

[iteyelmp]

Is there any solution to this problem? I get this error when I execute transactions synchronously in batches. After an error occurs, shutting down and restarting, and closing the browser will not work. You can only uninstall and reinstall.

[iteyelmp]

10 batch tasks are bound to trigger the error.

[JABirchall]

@JABirchall Any chance you figured this out?

Nope, uninstalling and reinstalling metamask fixed the issue. So maybe its a longeverty thing. Something (logs, data, vault, transcation, etc) gets too big and metamask cant load because of it. I had been using metamask for about 3 years before this error happened.

Sorry for late reply, but since i had fixed it by reinstalling i didnt bother replying.

[iteyelmp]

OK, thanks. But the wallet of the dapp user cannot be deleted. So I don't know how to fix this problem.