# Metamask become slower and slower and eventually died **URL:** \ **Category:** Support\ **Created:** [August 18, 2025, 3:13pm UTC](https://community.metamask.com/t/metamask-become-slower-and-slower-and-eventually-died/30658 "2025-08-18T15:13:01Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![abxc9](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@abxc9](https://community.metamask.com/u/abxc9)\ **Post date:** [August 18, 2025, 3:13pm UTC](https://community.metamask.com/t/metamask-become-slower-and-slower-and-eventually-died/30658/1 "2025-08-18T15:13:01Z")
In the latest versions the interface freezes on every click, becoming unusable, the settings are ignored. Has anyone even tried to run this? After the last update it completely died. **Version 12.23.1** I found same issue here: > > > \### Describe the bug > > Browser: Tor Browser \`\`\`14.5.5\`\`\` (based on Mozilla Firefo…x 128.13.0esr) > Metamask version: any version after \`\`\`12.18.3\`\`\` > > Metamask does not even prompt for password to unlock the wallet and stays in an infinite loop displaying the splash screen > > Reverting back to 12.18.3 makes it work again > > > \Image > > > > > > > \### Steps to reproduce > > 1. Download Tor browser > 2. Add metamask extension, version greater than 12.18.3 > 3. Open it > 4. The wallet stays in the fox launch screen forever > > \### Error messages or log output > > \`\`\`shell > > \`\`\` > > \### Detection stage > > In production (default) > > \### Version > > 13.x, 12.x > > \### Build type > > None > > \### Browser > > Other (please elaborate in the "Additional Context" section) > > \### Operating system > > MacOS > > \### Hardware wallet > > \_No response\_ > > \### Additional context > > Tor Browser \`\`\`14.5.5\`\`\` (based on Mozilla Firefox 128.13.0esr) > > \### Severity > > Critical severity - cannot use wallet Are you testing new versions on users? Interesting approach. Now you know it’s broken, need to revert to previous working version! Maybe new versions contain a fix and I should wait for the update? Nope. Here is the same behavior in the newest version 13.0.1 in a different environment: > > > \### Describe the bug > > My Metamask has suddenly stopped working from 12th August …possibly due to this upgrade. Here are error logs. > > Uncaught (in promise) s: Failed to connect to MetaMask > Uncaught (in promise) s: Failed to connect to MetaMask > Uncaught (in promise) s: Failed to connect to MetaMask > Uncaught (in promise) s: Failed to connect to MetaMask > SES\_UNCAUGHT\_EXCEPTION: null > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > SES\_UNCAUGHT\_EXCEPTION: Error: Extension context invalidated. > This browser doesn't support requestAnimationFrame. Make sure that you load a polyfill in older browsers. https://reactjs.org/link/react-polyfills > This browser doesn't support cancelAnimationFrame. Make sure that you load a polyfill in older browsers. https://reactjs.org/link/react-polyfills > Uncaught TypeError: Cannot read properties of undefined (reading 'getSelf') > > \### Expected behavior > > It does not even proceed to login screen which it should. > > \### Screenshots/Recordings > > \_No response\_ > > \### Steps to reproduce > > 1. Go to older MacOs chrome versions > 2. Start Metamask > 3. Keeps rotating endlessly without login > 4. > > \### Error messages or log output > > \`\`\`shell > > \`\`\` > > \### Detection stage > > In production (default) > > \### Version > > 13.0.1 > > \### Build type > > None > > \### Browser > > Chrome > > \### Operating system > > MacOS > > \### Hardware wallet > > \_No response\_ > > \### Additional context > > \_No response\_ > > \### Severity > > \_No response\_ So we can conclude that MetaMask is dead. ---
**Author:** ![Karina](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/karina/32/36428_2.png) [@Karina](https://community.metamask.com/u/Karina)\ **Post date:** [August 18, 2025, 5:45pm UTC](https://community.metamask.com/t/metamask-become-slower-and-slower-and-eventually-died/30658/2 "2025-08-18T17:45:20Z")
Hi! It‘s a known issue. Please contact MetaMask Support at [https://support.metamask.io/](https://support.metamask.io/ "https://support.metamask.io/") and click “Start a Conversation.” Once you click “Start a Conversation” a live chat bot will appear on your screen. It will give you an automated response at first, but afterwards you should be able to contact the support team directly. WE WILL NEVER SEND YOU DM TO OFFER SUPPORT REGARDING MetaMask HERE, PLEASE BE CAREFUL! ---
**Author:** ![abxc9](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@abxc9](https://community.metamask.com/u/abxc9)\ **Post date:** [August 20, 2025, 5:25pm UTC](https://community.metamask.com/t/metamask-become-slower-and-slower-and-eventually-died/30658/3 "2025-08-20T17:25:05Z")
I found that the total number of problems with MetaMask is more than 2000. Similar problems can hang for months without a solution, for example: > > > \### Describe the bug > > When I try to open the extension, it does not show the pa…ssword input field. It's just loading indefinitely. > > I checked the browser console using DevTools and found CSP-related errors and LavaMoat security-related logs. > > This issue is happening even though both my MetaMask extension and Firefox browser are fully updated. > > Since I do not have my secret recovery phrase or private key, I cannot restore the wallet elsewhere. My funds are completely locked unless this issue is fixed. > > Environment > > Browser: Firefox (latest version) > \-MetaMask Extension: Latest version from addons.mozilla.org > OS: Windows > Wallet Access: No secret recovery phrase or private key available > \-Issue Severity: Critical (funds locked, access completely blocked) > Steps to Reproduce > > Open Firefox (latest version) > Install MetaMask > Try to open the MetaMask extension > Observe: > Loading spinner appears > No password field is shown > Cannot interact with the extension > Console shows errors (see below) > Console Errors > > InstallTrigger is deprecated and will be removed in the future. runtime-lavamoat.js:13371:21 > onmozfullscreenchange is deprecated. runtime-lavamoat.js:13371:21 > onmozfullscreenerror is deprecated. runtime-lavamoat.js:13371:21 > Snow detected a new realm creation attempt in MetaMask. Performing scuttling on new realm. > Window moz-extension://381eeeb7-9878-4ae4-b17f-98ccafdf144a/background.html > use-snow.js:23:14 > Snow detected a new realm creation attempt in MetaMask. Performing scuttling on new realm. > Window moz-extension://381eeeb7-9878-4ae4-b17f-98ccafdf144a/background.html > use-snow.js:23:14 > Property eval will not be hardened because it is scuttled by LavaMoat protection. Visit https://github.com/LavaMoat/LavaMoat/pull/360 to learn more. sentry-install.js:1:750 > > WARNING: Missing strong random number source sentry-install.js:1:750 > > Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'wasm-unsafe-eval'” (Missing 'unsafe-eval') runtime-lavamoat.js:12237:15 > > Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'wasm-unsafe-eval'” (Missing 'unsafe-eval') runtime-lavamoat.js:5802:30 > > Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'wasm-unsafe-eval'” (Missing 'unsafe-eval') > > \### Expected behavior > > \_No response\_ > > \### Screenshots/Recordings > > !\[Image\](https://github.com/user-attachments/assets/e6901e6c-515a-4e6e-80b0-b2d50d8dfe75) > > \### Steps to reproduce > > Go to Firefox > Click on metamask extension > See its just loading non stop > > \### Error messages or log output > > \`\`\`shell > > \`\`\` > > \### Detection stage > > In production (default) > > \### Version > > updated > > \### Build type > > None > > \### Browser > > Firefox > > \### Operating system > > Windows > > \### Hardware wallet > > \_No response\_ > > \### Additional context > > Please resolve this issue as im having much funds inside it > > \### Severity > > \_No response\_ The team is actively working on the support of Bitcoin, Solana, even shitcoins, but not users. A great future where the next shitcoin update destroys your wallet and the team does nothing! If you play with tons of shitcoin shitcode, where is the rollback button? 1 Team has a working code. 2 The team releases an update for shitcoins, which breaks everything! 3 Rollback? No! Wait, maybe in a couple of months it will be resolved … or not. You should be happy with the additional support of shitcoins! Maybe there is something about the shutdown of MetaMask in the news? From the news you can find out that MetaMask did not die at all, but releases its stablecoin. I wonder how many months will the withdrawal of these stablecoins will occupy? **Is it legal when financial services become unavailable for months, and support responds with copy-paste? While team has a working code. So, guys you really crossed the line with your shitty experiments!** ---
**Author:** ![Coffee7643](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/coffee7643/32/36480_2.png) [@Coffee7643](https://community.metamask.com/u/Coffee7643)\ **Post date:** [August 21, 2025, 6:41am UTC](https://community.metamask.com/t/metamask-become-slower-and-slower-and-eventually-died/30658/4 "2025-08-21T06:41:25Z")
> [@abxc9](#): > > In the latest versions the interface freezes on every click, becoming unusable, the settings are ignored. Has anyone even tried to run this? Hi abxc9 and thank you for sharing this detailed feedback. Do you have a ticket open with support about this so they can take a more in depth look as Karina advised above? ---
**Author:** ![system](https://europe1.discourse-cdn.com/metamask/original/3X/3/8/3812168020a49f264784b1dbfcf12435abbb09ad.png) [@system](https://community.metamask.com/u/system)\ **Post date:** [September 17, 2025, 3:13pm UTC](https://community.metamask.com/t/metamask-become-slower-and-slower-and-eventually-died/30658/5 "2025-09-17T15:13:48Z")
Closed on September 17, 2025, 3:13pm UTC This topic was automatically closed after 30 days. New replies are no longer allowed.