Blank Extension Screen on Chrome/Firefox/Brave/etc.

[ERC1975]

Bounty: some users have reported experiencing a blank screen when the open the MetaMask extension in Chrome. This bounty is to identify a root cause of the issue that matches the symptoms and errors described below & to write a patch that fixes it.

---

I just downloaded and installed the Chrome Extension. However, when I click the fox in the upper right it opens a box/window to the right that is completely empty. It does not appear that the extension is operating correctly.

I'm on a Mac and using Chrome (most recent update).

Thanks,
ERC

[bdresser]

@ERC1975 sorry to hear that. Could you help us debug by sending your background logs? There are instructions about halfway down this support article. You can post them here, or send to [email protected] and mention this issue URL.

[myn]

Getting same issue on my Mac too.

[myn]

[myn]

Background Page

[Strernd]

Got this same issue on Chrome, Brave and Firefox.
#4782

[Strernd]

Reinstalling Metamask fixed it for me on Chrome

[estebanmino]

somehow I was able to reproduce the last error showed in the picture. From development I got this

It corresponds to the method setupPublicConfig of metamaskController. The app did crash but I tried to reopen it and it worked fine.

[bdresser]

@Strernd next time you experience this, could you check the popup logs and background logs? Curious if you're getting the same error Esteban found, or something different. Sorry for the trouble & thanks for your help!

[tritone11]

Same problems here, on Chrome on Windows 10, I managed to produce this error with the background logs

I hope this helps somehow, these crashes are haunting me since 2 weeks

[tritone11]

Similar as above

EDIT:
Inspecting the extension while running, it freezes and it stays white when there is any call to the infura API. Althought the chrome inspector says the various calls like eth_getBlockByNumber, eth_getTransactionByHash, mainnet, blacklist ecc. take from 50ms to 200ms, most of the time I see them in pending for 20-30 seconds.
After blocking the domain api.infura.io the extension run smoothly without freezing or without showing the blank screen (without being able to log in or use it, obviously).

Not able to change the network

[tritone11]

I managed to recover my seed phrase from the crashing, whitescreening Metamask, then reinstall Metamask to get everything fixed.

I set up a private ethereum network with geth and rpc enabled, then stop the internet connection of my computer. Launching metamask, it wasn't able to find infura, so it started without problems and I set up a custom RPC from the metamask dropdown pointing to my ethereum node. Metamask connected to it, I logged in and took my seed phrase from the settings.

Then, I reinstalled Metamask and restored my wallet with the seed phrase.

I guess this would work with any public ethereum node, even testnet nodes, just disable your internet connection or block the infura api, open metamask, re-establish the connection and connect with custom rpc

EDIT: for anybody unable to find a public node to recover your seed or unable to set up your own node, I can open mine shortly to let you recover your seed, just contact me.

[bdresser]

from standup:

• often happens when a process (like the background process) ends unexpectedly, sometimes a stream from the UI to background
• worth cross-referencing with Sentry to see if there's anything insightful

[bdresser]

could be related to https://sentry.io/metamask/metamask/issues/562285240/?query=is:unresolved (cc @jennypollack)

[bdresser]

@tritone11 thanks for the detailed rundown. Could I ask you to also send along your state logs to [email protected]? They'll help us identify the latest version of a particular migration that might be causing issues.

Instructions on how to get your state logs are here, assuming you're still able to access the UI as you described. Make sure you mention this issue number (4894) in your note. Thanks again for the help!

cc @whymarrh @alacrity26

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.45 ETH (181.59 USD @ $403.53/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $24,966.41 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

💰 A crowdfund contribution worth 0.05000 ETH (20.5 USD @ $409.98/ETH) has been attached to this funded issue from @.💰

Want to chip in also? Add your own contribution here.

[gitcoinbot]

@shad-k Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• warning (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[shad-k]

@bdresser can you send me any logs that you might have received regarding this. I have been trying to recreate this issue but have failed to do so thus far.

[bdresser]

@shad-k haven't received any reliable state logs on this.

above in this thread, most folks either see error: write after end or Error: PortDuplexStream -disconnected.

@estebanmino any detail to add?

[estebanmino]

@shad-k the PortDuplexStream error is generated here

metamask-extension/app/scripts/lib/port-stream.js

Line 67 in e2be22a

PortDuplexStream.prototype._write = function (msg, encoding, cb) {

and it seems to be a disconnection between background and UI.
The write after end error is originated here

metamask-extension/app/scripts/metamask-controller.js

Line 1272 in e2be22a

setupPublicConfig (outStream) {

[mqklin]

I tried to fix extension code but broke something and lost all ETHs, fortunately I didn't have much there

[tritone11]

Hi, I'm getting this issue, is there a process for getting the private key or seed phrase out when the UI is unusable?

Here I disabled infura and connected metamask to another node, recovering the private key
#4894 (comment)

[tuxxy]

I'm experiencing this issue as well with Firefox on Arch Linux. The problem persists even after removing the extension and reinstalling it (I also tried a machine restart). Metamask seems completely unusable for me at this time...

[nickgon]

Try removing the extension, disabling any ad blocker, and then reinstalling.

[tsylana1]

@tritone11 - how did you go about disabling Infura? I have a sizable amount lost in a wallet where I can't seem to find my seed phrase and would be more than happy to share some if you can fix my issue

[tritone11]

@tritone11 - how did you go about disabling Infura? I have a sizable amount lost in a wallet where I can't seem to find my seed phrase and would be more than happy to share some if you can fix my issue

Just unplug your internet connection and open metamask, or in your file host disable the infura domain or whatever domain your metamask is trying to reach. Metamask will launch without problems and bypass the whitescreen/loading page and you can recover your seed phrase (if your problem is there.)

[tsylana1]

@tritone11 - thanks... seems this didn't fix my issue unfortunately.... onto the next plan then...

[presentday01]

@tritone11 - thanks... seems this didn't fix my issue unfortunately.... onto the next plan then...

this is driving me insane! if you hear of anything please quote/tag me. I think im gonna try some of the weirder methods to get it back, this literally happened after the update. I had made a new wallet for safety but didn't save the private key string in time. literally worst timing ever

[bamacryp]

I managed to recover my seed phrase from the crashing, whitescreening Metamask, then reinstall Metamask to get everything fixed.

I set up a private ethereum network with geth and rpc enabled, then stop the internet connection of my computer. Launching metamask, it wasn't able to find infura, so it started without problems and I set up a custom RPC from the metamask dropdown pointing to my ethereum node. Metamask connected to it, I logged in and took my seed phrase from the settings.

Then, I reinstalled Metamask and restored my wallet with the seed phrase.

I guess this would work with any public ethereum node, even testnet nodes, just disable your internet connection or block the infura api, open metamask, re-establish the connection and connect with custom rpc

EDIT: for anybody unable to find a public node to recover your seed or unable to set up your own node, I can open mine shortly to let you recover your seed, just contact me.

Are you still available because I just had this happen to me and I cannot afford to lose my wallet ...especially right now...I definitely need it restored. Thank you

[bamacryp]

I don't understand???? Do you have a solution for this? I would really appreciate some help as I cannot access my wallet and cannot afford to replace it

…

On Tue, Jan 4, 2022 at 10:42 AM DomeSs97 ***@***.***> wrote: [image: 20220104_163708] <https://user-images.githubusercontent.com/20913037/148093038-60a283db-bbac-42f6-a418-eb6121d76ecd.jpg> Hello, any solution for this? If I use this command in console chrome.storage.local.get('data', result => { var vault = result.data.KeyringController.vault console.log(vault) }) It's only say undefinded. — Reply to this email directly, view it on GitHub <#4894 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVN27GBWQITLADZQYV3WIITUUMPPLANCNFSM4FMJHZLQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[sahand525]

Metamask white/Blank Screen on Chrome version 10.9.2

[bamacryp]

I did not understand....are you saying you have a solution? <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

…

On Thu, Feb 10, 2022 at 2:27 AM sahand525 ***@***.***> wrote: Metamask white/Blank Screen on Chrome version 10.9.2 — Reply to this email directly, view it on GitHub <#4894 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVN27GBBERFSJNEAFKVGBC3U2NZFVANCNFSM4FMJHZLQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[anonqoder]

It is simply a disgrace such a serious issue can go unfixed for so long. There is really no will to fix it, plenty of users have the issue and could reproduce it, devs could asked users for more logs and troubleshooting. It is simply negligence at this point

You know what? SCREW METAMASK

What wallet should I migrate to? It should run on a Mac (no cellphone pls), be software-based (not willing to buy a hardware wallet) and should provide support for multiple accounts, tokens and interact with smart contracts. Shill to me (and to the other affect users) the alternative!

[Kamikozz]

Still reproducing #15000 (comment)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.