[Bug]: Completely unusable Metamask infinite load about metamask-extension HOT 43 OPEN

@nelwincatalogo The problem you are seeing is unique to chrome versions 122 and later. If you install the stable or beta chrome build (v120 or v121), MetaMask should work fine. We are currently working on solving the problem introduced with chrome 122

from metamask-extension.

Same issue, infinite loading upon opening metamask extension

Chrome Dev Version:
Version 122.0.6238.2 (Official Build) dev (64-bit)

Metamask Version:
11.7.3

Console Errors:

from metamask-extension.

Thanks @nostitos ! To clarify, we are able to reproduce on Chrome Canary, and a fix is on the way. We are sorry for the inconvenience, and advise that you use Chrome stable or beta in the meantime. If you have not backed up your secret recovery phrase and need help recovering it from your Chrome Canary install, please contact our support team and ask for help (click "Resources" => "Support" on our website, metamask.io)

We have been unable to reproduce the issue on Firefox so far.

Chrome Beta was just updated to Version 122.0.6261.6 (Official Build) beta (64-bit) and MetaMask 11.7.4 has infinite loading problem. Please ship fix ASAP.

from metamask-extension.

from metamask-extension.

Setting up Sentry Remote Error Reporting for 'production': SENTRY_DSN sentry-install.js:1:2889
Removing unpermitted intrinsics runtime-lavamoat.js:4079:15
Snow detected a new realm creation attempt in MetaMask. Performing scuttling on new realm. 
Window moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/popup.html
use-snow.js:23:14
Snow detected a new realm creation attempt in MetaMask. Performing scuttling on new realm. 
Window moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/popup.html
use-snow.js:23:14
Content-Security-Policy: The page’s settings blocked the loading of a resource at eval (“script-src”). runtime-lavamoat.js:10114:15
Content-Security-Policy: The page’s settings blocked the loading of a resource at eval (“script-src”). runtime-lavamoat.js:4381:30
Uncaught (in promise) Error: An unexpected error occurred
undefined
Uncaught (in promise) Error: An unexpected error occurred
undefined
SES_UNHANDLED_REJECTION: (Error#1) sentry-install.js:1:693
    t moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    _ moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    levelMethod moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6929
    handleRejection moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7285
    finalizeDroppedPromise moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7058
Error#1: An unexpected error occurred sentry-install.js:1:693
    t moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    _ moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    logError moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6890
    logSubErrors moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6833
    levelMethod moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6931
    handleRejection moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7285
    finalizeDroppedPromise moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7058
<empty string> sentry-install.js:1:693
    t moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    _ moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    logError moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6912
    logSubErrors moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6833
    levelMethod moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6931
    handleRejection moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7285
    finalizeDroppedPromise moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7058
SES_UNHANDLED_REJECTION: (Error#2) sentry-install.js:1:693
    t moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    _ moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    levelMethod moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6929
    handleRejection moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7285
    finalizeDroppedPromise moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7058
Error#2: An unexpected error occurred sentry-install.js:1:693
    t moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    _ moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    logError moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6890
    logSubErrors moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6833
    levelMethod moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6931
    handleRejection moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7285
    finalizeDroppedPromise moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7058
<empty string> sentry-install.js:1:693
    t moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    _ moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/sentry-install.js:1
    logError moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6912
    logSubErrors moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6833
    levelMethod moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:6931
    handleRejection moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7285
    finalizeDroppedPromise moz-extension://6b7107bc-708b-4c4a-9cbc-0abd14ff7c20/runtime-lavamoat.js:7058
```

Firefox log in case it helps

from metamask-extension.

#22462

This looks urgent to me

from metamask-extension.

@danjm

from metamask-extension.

@tdev00 @harleauxcarrera

from metamask-extension.

@kevinghim

from metamask-extension.

@jeffbzs can you inspect the background console for errors?

1. Go to about:debugging#/runtime/this-firefox
2. Click the "Inspect" button next to MetaMask
3. Click the "Console" tab

and share any error messages you see with us

from metamask-extension.

@nostitos What browser version are/were you using when you saw this problem?

from metamask-extension.

@jeffbzs can you inspect the background console for errors?

1. Go to about:debugging#/runtime/this-firefox
2. Click the "Inspect" button next to MetaMask
3. Click the "Console" tab

and share any error messages you see with us

from metamask-extension.

@jeffbzs Thank-you. Can you now click the arrows next to SES_UNHANDLED_REJECTION and Error#1 and Error#2, and share what is shown after those are opened?

from metamask-extension.

@jeffbzs Thank-you. Can you now click the arrows next to SES_UNHANDLED_REJECTION and Error#1 and Error#2, and share what is shown after those are opened?

from metamask-extension.

Thanks. And can you tell me when did you last see MetaMask working? And did anything change about your browser or MetaMask setup between when it was last working and when you first saw this problem?

from metamask-extension.

Thanks. And can you tell me when did you last see MetaMask working? And did anything change about your browser or MetaMask setup between when it was last working and when you first saw this problem?

The last time Metamask was working was 2 days ago, nothing has changed in my browser, I haven't done anything.

from metamask-extension.

Do you know if the MetaMask version updated during that time? This is unlikely, as we have not published a new version to firefox in over 3 weeks, but I'm checking in case you ever manually update.

from metamask-extension.

Do you know if the MetaMask version updated during that time? This is unlikely, as we have not published a new version to firefox in over 3 weeks, but I'm checking in case you ever manually update.

No, Metamask has not been updated in that timeframe

from metamask-extension.

@jeffbzs what version of firefox are you using?

from metamask-extension.

@jeffbzs what version of firefox are you using?

121.0.1 (64-bit)

from metamask-extension.

@jeffbzs what version of firefox are you using?

Do you think it’s possible to find a solution for this problem?

from metamask-extension.

Tried uninstalling the extension and installing again, same issue

from metamask-extension.

@jeffbzs I believe we will be able to solve your problem, but it is unclear how long it will take. I will be trying to reproduce your problem on firefox 121 today

from metamask-extension.

Same problem in Google Chrome. Appeared on January 13, 2024. During this time I reinstalled the extension, it did not help. Today the browser was updated also did not solve the problem.
As far as I remember, the bug appeared after the extension froze and the browser was forced to restart.

Chrome Dev Version:
122.0.6251.0 (Official build), canary (64 bit)

Metamask Version:
11.7.3

Console Errors:

from metamask-extension.

@gitmaxton did you see my above comment?

The problem you are seeing is unique to chrome versions 122 and later. If you install the stable or beta chrome build (v120 or v121), MetaMask should work fine. We are currently working on solving the problem introduced with chrome 122

If you install chrome stable or beta, you should be able to get MetaMask to work

from metamask-extension.

@gitmaxton did you see my above comment?

The problem you are seeing is unique to chrome versions 122 and later. If you install the stable or beta chrome build (v120 or v121), MetaMask should work fine. We are currently working on solving the problem introduced with chrome 122

If you install chrome stable or beta, you should be able to get MetaMask to work

hi @, is there any news?

from metamask-extension.

Issue potentially related: #22589

from metamask-extension.

Hi @danjm, if possible, please give us some updates, we are all worried, cause our money are being stuck..

from metamask-extension.

@jeffbzs We are still investigating. This is not happening to many users and we cannot reproduce it, so it will take time to find the cause of the problem. Can you check whether the same errors as shown here #22589 (about "IndexDB") are showing up in your console?

Also, it may make sense for you to uninstall and reinstall, or install metamask in a different browser. But only do that if you have your secret recovery phrase, or individually imported private keys, backed up. Do you have those backed up?

from metamask-extension.

from metamask-extension.

@jeffbzs We are still investigating. This is not happening to many users and we cannot reproduce it, so it will take time to find the cause of the problem. Can you check whether the same errors as shown here #22589 (about "IndexDB") are showing up in your console?

Also, it may make sense for you to uninstall and reinstall, or install metamask in a different browser. But only do that if you have your secret recovery phrase, or individually imported private keys, backed up. Do you have those backed up?

I don't have a backup of the imported private keys

I don't understand which one you are talking about (about "IndexDB")

from metamask-extension.

Thanks @nostitos ! To clarify, we are able to reproduce on Chrome Canary, and a fix is on the way. We are sorry for the inconvenience, and advise that you use Chrome stable or beta in the meantime. If you have not backed up your secret recovery phrase and need help recovering it from your Chrome Canary install, please contact our support team and ask for help (click "Resources" => "Support" on our website, metamask.io)

We have been unable to reproduce the issue on Firefox so far.

from metamask-extension.

The v11.7.5 release fixes this. It has been submitted to chrome and we will roll it out as soon as possible.

I agree that we need to include Chrome Canary and Chrome Beta in our testing, and we will be improving our processes to do this.

from metamask-extension.

The v11.7.5 release fixes this. It has been submitted to chrome and we will roll it out as soon as possible.

I agree that we need to include Chrome Canary and Chrome Beta in our testing, and we will be improving our processes to do this.

The update seems to have deleted the seed. Asking me to create or restore a wallet.
I do not have the backup because I thought having it in multiple chrome on multiple device was safe, All Canary and buggy.

from metamask-extension.

@nostitos have you updated on multiple browsers and is it "Asking me to create or restore a wallet" on multiple browsers?

The seed is probably not deleted, but maybe your browser data is corrupted somehow.

If you are interested, we could get on a zoom call sometime this week to try to understand what has happened to your extension data.

from metamask-extension.

use Chrome stable

Can you submit update to Edge Add-ons as well? I'm experiencing the same problem.

from metamask-extension.

@nostitos have you updated on multiple browsers and is it "Asking me to create or restore a wallet" on multiple browsers?

The seed is probably not deleted, but maybe your browser data is corrupted somehow.

If you are interested, we could get on a zoom call sometime this week to try to understand what has happened to your extension data.

has there been any update on this because this is what happened to me, pretty much exactly.

from metamask-extension.

The same problem is happening to me. I am using a firefox 122.0 and Metamask is loading forever... By now, Metamask extenssion in Firefox browser is completely useless..

from metamask-extension.

@danjm how's it going with the solution to my problem?

from metamask-extension.

from metamask-extension.

I'm having this exact same problem in Firefox....

from metamask-extension.

same exact error here as reported in firefox

from metamask-extension.

Same issue happening on Brave right now. I would like to avoid removing the extension and adding it back because I really don't want to lose private keys that I may have forgotten to write down.

from metamask-extension.