search

MetaMask / metamask-extension

:globe_with_meridians: :electric_plug: The MetaMask browser extension enables browsing Ethereum blockchain enabled websites
https://metamask.io
Other
11.57k stars 4.73k forks source link

[Bug]: Completely unusable Metamask infinite load #22533

Open jeffbzs opened 4 months ago

jeffbzs commented 4 months ago

Describe the bug

Nothing happens, just a download with no inscriptions

Expected behavior

The wallet should open..

Screenshots/Recordings

image

Steps to reproduce

Simply opening the extension

Error messages or log output

No response

Version

11.7.2

Build type

None

Browser

Firefox

Operating system

Windows

Hardware wallet

No response

Additional context

No response

Severity

No response

nostitos commented 4 months ago

https://github.com/MetaMask/metamask-extension/issues/22462

This looks urgent to me

jeffbzs commented 4 months ago

@danjm

jeffbzs commented 4 months ago

@tdev00 @harleauxcarrera

jeffbzs commented 4 months ago

@kevinghim

danjm commented 4 months ago

@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

danjm commented 4 months ago

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

jeffbzs commented 4 months ago

@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

image

danjm commented 4 months ago

@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?

jeffbzs commented 4 months ago

@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?

image

danjm commented 4 months ago

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?

jeffbzs commented 4 months ago

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.

danjm commented 4 months ago

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.

jeffbzs commented 4 months ago

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

danjm commented 4 months ago

@jeffbzs what version of firefox are you using?

jeffbzs commented 4 months ago

@jeffbzs what version of firefox are you using?

121.0.1 (64-bit)

jeffbzs commented 4 months ago

@jeffbzs what version of firefox are you using?

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

nelwincatalogo commented 4 months ago

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: image

nelwincatalogo commented 4 months ago

Tried uninstalling the extension and installing again, same issue

danjm commented 4 months ago

@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

danjm commented 4 months ago

@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

gitmaxton commented 4 months ago

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: bagii

danjm commented 4 months ago

@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

jeffbzs commented 4 months ago

@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?

gauthierpetetin commented 4 months ago

Issue potentially related: https://github.com/MetaMask/metamask-extension/issues/22589

jeffbzs commented 4 months ago

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

danjm commented 4 months ago

@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 https://github.com/MetaMask/metamask-extension/issues/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?

nostitos commented 4 months ago

To reproduce? Try running metamask on Chrome Canary.

It does the same thing on multiple devices.

On Mon, Jan 22, 2024, 10:30 Dan J Miller @.***> wrote:

@jeffbzs https://github.com/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 https://github.com/MetaMask/metamask-extension/issues/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?

— Reply to this email directly, view it on GitHub https://github.com/MetaMask/metamask-extension/issues/22533#issuecomment-1904248579, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSB6MEAZWGJVRMWKJTU7ZDYP2AYLAVCNFSM6AAAAABBZT5UTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGI2DQNJXHE . You are receiving this because you were mentioned.Message ID: @.***>

jeffbzs commented 4 months ago

@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")

Gudahtt commented 4 months ago

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.

mikeinweb commented 4 months ago

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.

nostitos commented 4 months ago

Seems like you should also test on canary to catch problems early since whatever problem there is likely to end up in main branch.

On Thu, Jan 25, 2024, 15:43 Mike @.***> wrote:

Thanks @nostitos https://github.com/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.

— Reply to this email directly, view it on GitHub https://github.com/MetaMask/metamask-extension/issues/22533#issuecomment-1910967550, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSB6MAJDNIZMK62OQJ2UJ3YQK7YLAVCNFSM6AAAAABBZT5UTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJQHE3DONJVGA . You are receiving this because you were mentioned.Message ID: @.***>

danjm commented 4 months ago

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.

nostitos commented 4 months ago

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.

danjm commented 4 months ago

@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.

DockedFerret800 commented 3 months ago

use Chrome stable

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

mmmro commented 3 months ago

@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.

rlarbac commented 3 months ago

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..

jeffbzs commented 3 months ago

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

nostitos commented 3 months ago

I can't do any more testing on my end since I created a new seed. The data was gone after the update.

If I were someone affected with money on the line I'd backup whatever data is in the extension before they push an update that might clear it out.

On Tue, Feb 6, 2024, 03:15 jeffbzs @.***> wrote:

@danjm https://github.com/danjm how's it going with the solution to my problem?

— Reply to this email directly, view it on GitHub https://github.com/MetaMask/metamask-extension/issues/22533#issuecomment-1928987964, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSB6MGYFYFADS232LT7C4DYSHRDJAVCNFSM6AAAAABBZT5UTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYHE4DOOJWGQ . You are receiving this because you were mentioned.Message ID: @.***>

digitalnomad91 commented 3 months ago

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

cclobo2 commented 3 months ago

same exact error here as reported in firefox

cclobo2 commented 3 months ago 
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

justinasfour04 commented 3 months ago

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.

xuyenvuong commented 3 months ago

Same issue with Brave and MM v11.7.2. Tried to disable/enable the extension, restart browser, restart PC, still not working. I didn't try to reinstall MM due to the hassle.

danjm commented 2 months ago

@justinasfour04 @xuyenvuong Make sure to update to the latest version of MetaMask. Anyone experiencing this problem on Chrome and Brave over the past 3 weeks has fixed it by updating to v11.7.5 or later.

justinasfour04 commented 2 months ago

@danjm how do I force an update?

xuyenvuong commented 2 months ago

@justinasfour04 @xuyenvuong Make sure to update to the latest version of MetaMask. Anyone experiencing this problem on Chrome and Brave over the past 3 weeks has fixed it by updating to v11.7.5 or later.

Thank you @danjm . Will do.

xuyenvuong commented 2 months ago

@danjm how do I force an update?

@justinasfour04 - You can right click on the MM extension icon, then select Manage extension, Next, turn on the Developer mode, then click Update. After the update, you can now log back into MM. Then you can turn off Developer mode.

cryptodigi commented 2 months ago

got this issue on mm version 11.11.0 please deploy another update

justinasfour04 commented 2 months ago

Now I have a stuck approval on a transaction and my settings are greyed out I can't use metamask now on my brave browser