[Bug]: metamask not loading

[carlmoss22]

Describe the bug

on windows 10 and chromium (all updated) metamask wont load. when i click on investigate it shows this error. ReferenceError#23: LavaPack is not defined

i uninstalled and reinstalled but nothing worked. can you help me out?

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

just not loading

Error messages or log output

ReferenceError#23: LavaPack is not defined

Version

latest on chromium webstore

Build type

None

Browser

Chrome

Operating system

Windows

Hardware wallet

No response

Additional context

No response

Severity

No response

[carlmoss22]

this is the screenshot.

[anaamolnar]

Hello, @carlmoss22. Thanks for reporting! Do you remember anything specific you did before this? Could you please attempt disabling and re-enabling the extension from the Manage extension and see if the issue continues to occur? Do you have your secret recovery phrase backed up? Thanks!

[carlmoss22]

thank you for answer. i did not do anything specific. i turned it on and off and even reinstalled it. without a solution. its just not loading.

[bekju]

same, it stopped working for me on Google Chrome Dev build. On normal google chrome it works, reinstall works too, on chrome dev it just randomly stopped working, reinstall doesn't work either from chrome web store or manually loading, same errors as above. Maybe chrome dev updated and broke the extension?

[danjm]

@carlmoss22 what version of chrome are you using?

[danjm]

@bekju What exactly do you mean by "Google chrome dev build"? Can you share the steps of how you installed / set-up the "Google chrome dev build"?

[WoeOm]

• version 122.0.6250.0 canary (arm64)

[danjm]

Anyone experiencing this problem is likely using chrome version 122 or later (e.g. a canary or dev build). If you install the current stable or beta versions (120 or 121) of chrome, this problem should not occur. We are currently working on solving the incompatibility introduced with chrome 122.

[carlmoss22]

@carlmoss22 what version of chrome are you using?

i am on 122. still nothing works. It's a bit annoying that it's not possible to find a solution in more than 2 weeks. everybody tells you to update your browser and than.... ;-)

[cargo8]

Any update on this issue? The breaking update (122) seems to have now hit Chrome Beta

[mz3944]

Anyone experiencing this problem is likely using chrome version 122 or later (e.g. a canary or dev build). If you install the current stable or beta versions (120 or 121) of chrome, this problem should not occur. We are currently working on solving the incompatibility introduced with chrome 122.

Is this possible to do safely, without losing the Metamask profile while downgrading the Chrome version?

[lucasvo]

Bump on this - Chromium's 122 release went out and it's likely going to affect a lot of users: https://developer.chrome.com/blog/new-in-chrome-122

[gauthierpetetin]

Hello @carlmoss22 , is this still an issue? Or is it a duplicate of this issue which is now solved?

[coachbjork]

I have the same issue, on two machines.

Both have been idle for a few months, working just fine before. Started them, updated chrome (and other softwares). Then Metmask is stuck in this loop.

Machine 1: Windows, Chrome Machine 2: Linux Mint, Chrome

Both running chrome: Version: 123.0.6312.86 (Official Build) (64-bit) Both running Metamask Version: Metamask: v11.4.1

Edit:

• Removing the plugin, and then installing it again solved any problem. But that means I need to re-import the wallet(s) etc.

[paradigmsh]

Update Metamask to the latest version, then it works!

How to update? Enable Developer Option in Extensions panel and you can update inside individual extension page.

[gund]

This issue started happening to me today, I'm using latest stable Chrome Version 126.0.6478.127 (Official Build) (64-bit) on latest Windows 11 with latest Metamask extension. But I cannot see any errors in the console and dev extensions do not report any errors, just loading screen stuck forever... Is this issue being looked into?

EDIT: I see a few warnings in the console but no errors:

EDIT2: Seems like after disabling and enabling the extension it's back to working fine, very weird...