Version 8.1.9 freezes while importing keystore #10113

eiabea · 2020-12-19T22:43:11Z

Describe the bug
After importing a metamask wallet from a seed and trying to import a keystore json file into this account, metamask freezes until chrome asks to "wait" or "exit" the tab

Steps to reproduce (REQUIRED)
Steps to reproduce the behavior, libraries used with version number, and/or any setup information to easily reproduce:

Install metamask 8.1.9
Import wallet from seed
Click on import account
Select type "Json"
Enter your password
Experience a freeze of the metamask tab

Expected behavior
Account gets imported

Browser details (please complete the following information):

OS: Linux
Hardware Wallet: No
Browser: Version 87.0.4280.66 (Official Build) Arch Linux (64-bit)
MetaMask Version: 8.1.9

Additional context (Error Messages, etc.)
Downgrading MetaMask to 8.1.5 fixed the issue

The text was updated successfully, but these errors were encountered:

tmashuang · 2020-12-19T22:54:26Z

After installing and import, but before getting to the home page, are you accepting participating in the metrics page? Sounds like a #10097.

eiabea · 2020-12-19T22:56:23Z

After installing and import, but before getting to the home page, are you accepting participating in the metrics page? Sounds like a #10097.

No i haven't actually

tmashuang · 2020-12-19T23:00:10Z

Where was the json file account created? I've imported a json account created from Mycrypto.

eiabea · 2020-12-20T00:15:09Z

Where was the json file account created? I've imported a json account created from Mycrypto.

directly in geth

shoenseiwaso · 2020-12-23T10:19:02Z

I'm seeing the same issue with MetaMask, Chrome on macOS. MetaMask pegs a CPU core for several minutes until killed when attempting to import a JSON keystore file.

adamsoffer · 2021-01-01T19:20:01Z

Can confirm this on my end as well. Brave on macOS. Running Big Sur on the Apple M1.

miki-bgd-011 · 2021-01-02T23:48:36Z

Same issue, Ubuntu 20, Chrome 87.0.4280.88.

davidgamero · 2021-01-05T05:52:50Z

Thought I had this same issue on Intel Mac running Big Sur, CPU at 100% and fan lifting off. Metamask extension completely unresponsive. About 15min later it pops up and wallet was imported. Used to import from JSON instantly
Chrome 87.0.4280.88

kyrogue · 2021-01-06T16:27:23Z

same issue happening, on chrome 87.0.4280.88 , metamask 8.1.9 , when importing JSON key it hangs and never recovers

rekmarks · 2021-01-06T18:50:20Z

8.1.10 is live on Firefox and is rolling out to Chrome and Brave as we speak. Can someone please confirm whether the issue persists with the new version?

davidgamero · 2021-01-06T19:34:01Z

I was unable to reproduce the issue before but I can confirm my configuration continues to import wallets with the same freezing behavior on 8.1.10

rekmarks · 2021-01-06T21:15:03Z

Thank you. We just tried changing an Infura API configuration. We're not sure how long it will take to have an effect, but we may see some improvements in the next 24 hours, potentially much sooner. We will continue to monitor this issue for your feedback.

Deepcryptodive · 2021-01-17T11:18:47Z

Same issue!

Metamask 8.1.11
Both on Chrome & Brave
Both using the standard Infura RPC, and a custom RPC
Linux

d3v0n-m · 2021-01-17T13:13:53Z

I´ve got the same issue with Chrome (up-to-date Version 87.0.4280.141 ) and the latest (first ever installed) version of Metamask (Version 8.1.1.1) on macOS BigSur. Wanted to import an fresh Account, created yesterday locally with geth. Tried to import the json-File.

Thanks in advance.

rekmarks · 2021-01-18T00:05:50Z

I have reproduced the freezing locally in Chrome on develop while importing a wallet file created by geth account new. We are investigating the cause and will report back once we have more information.

eordano · 2021-01-29T17:24:54Z

Hi there, I am also experiencing this issue.

It was working fine last week, until I upgraded Chrome (current: 88.0.4324.96) and now it freezes, with no errors AFAIK.

Heads up, 9.0.4 seems to trigger this error when loading unpacked:

rekmarks · 2021-02-02T01:34:36Z

Here are my findings from reproducing this issue. When importing an account from a JSON file, we end up making this call to ethereumjs-wallet. The extension freezes on this line in that dependency. Ultimately I believe it hangs somewhere in the smix function in the scryptsy package. The extension recovers on a reload of the background process.

The current versions of the aforementioned dependencies were introduced in #9725. That was merged in October/November 2020. It's likely that this functionality has been broken since then. Importing a wallet from a JSON file works with the parent commit of the merge for #9725.

We don't yet have a timeline for a fix, but it should hopefully be straightforward. We will update this issue if we find anything else, but may just close it when a fix it merge. It should then go out in the subsequent release.

honsa · 2021-02-15T10:25:49Z

Still a game breaking issue the background logs, a lot of 3. party issues:

initSentry.js:1 Setting up Sentry Remote Error Reporting for 'production': SENTRY_DSN initSentry.js:8 Removing intrinsics.Promise.any initSentry.js:8 Removing intrinsics.Reflect.@@toStringTag initSentry.js:8 Removing intrinsics.%StringPrototype%.replaceAll bg-libs.js:16 Invalid asm.js: Unexpected token initSentry.js:8 MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 "update" listeners added. Use emitter.setMaxListeners() to increase limit. (anonymous) @ initSentry.js:8 api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED initSentry.js:8 MetaMask - Account Tracker single call balance fetch failed Object (anonymous) @ initSentry.js:8 api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED ipfs.3box.io/config?address=0x69441dc0d22365b7f8108b43fe4299c865f50903:1 Failed to load resource: the server responded with a status of 404 () api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED api.segment.io/v1/batch:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/initSentry.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/bg-libs.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/background.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME initSentry.js:1 [Violation] 'setInterval' handler took 53ms initSentry.js:1 POST https://api.segment.io/v1/batch net::ERR_NAME_NOT_RESOLVED (anonymous) @ initSentry.js:1 (anonymous) @ initSentry.js:8 (anonymous) @ background.js:18 t.exports @ background.js:18 t.exports @ background.js:18 Promise.then (async) c.request @ background.js:18 (anonymous) @ background.js:18 flush @ background.js:12 c @ initSentry.js:1 setTimeout (async) (anonymous) @ initSentry.js:1 enqueue @ background.js:12 page @ background.js:12 trackPage @ background.js:1 (anonymous) @ background.js:1 c.apply @ background.js:51 c.handle @ background.js:51 a.handle @ background.js:51 a.write @ background.js:51 m @ background.js:116 h @ background.js:34 a.emit @ background.js:34 _ @ background.js:116 w @ background.js:116 v.push @ background.js:116 _write @ background.js:110 v @ background.js:116 (anonymous) @ background.js:116 b.write @ background.js:116 m @ background.js:116 h @ background.js:34 a.emit @ background.js:34 _ @ background.js:116 w @ background.js:116 v.push @ background.js:116 _onMessage @ background.js:80 (anonymous) @ background.js:80 initSentry.js:1 [Violation] 'setInterval' handler took 53ms initSentry.js:1 POST https://api.segment.io/v1/batch net::ERR_NAME_NOT_RESOLVED (anonymous) @ initSentry.js:1 (anonymous) @ initSentry.js:8 (anonymous) @ background.js:18 t.exports @ background.js:18 t.exports @ background.js:18 Promise.then (async) c.request @ background.js:18 (anonymous) @ background.js:18 flush @ background.js:12 c @ initSentry.js:1 setTimeout (async) (anonymous) @ initSentry.js:1 enqueue @ background.js:12 page @ background.js:12 trackPage @ background.js:1 (anonymous) @ background.js:1 c.apply @ background.js:51 c.handle @ background.js:51 a.handle @ background.js:51 a.write @ background.js:51 m @ background.js:116 h @ background.js:34 a.emit @ background.js:34 _ @ background.js:116 w @ background.js:116 v.push @ background.js:116 _write @ background.js:110 v @ background.js:116 (anonymous) @ background.js:116 b.write @ background.js:116 m @ background.js:116 h @ background.js:34 a.emit @ background.js:34 _ @ background.js:116 w @ background.js:116 v.push @ background.js:116 _onMessage @ background.js:80 (anonymous) @ background.js:80 initSentry.js:1 POST https://api.segment.io/v1/batch net::ERR_NAME_NOT_RESOLVED (anonymous) @ initSentry.js:1 (anonymous) @ initSentry.js:8 (anonymous) @ background.js:18 t.exports @ background.js:18 t.exports @ background.js:18 Promise.then (async) c.request @ background.js:18 (anonymous) @ background.js:18 flush @ background.js:12 c @ initSentry.js:1 setTimeout (async) (anonymous) @ initSentry.js:1 enqueue @ background.js:12 track @ background.js:12 (anonymous) @ background.js:1 _track @ background.js:1 trackEvent @ background.js:1 (anonymous) @ background.js:1 c.apply @ background.js:51 c.handle @ background.js:51 a.handle @ background.js:51 a.write @ background.js:51 m @ background.js:116 h @ background.js:34 a.emit @ background.js:34 _ @ background.js:116 w @ background.js:116 v.push @ background.js:116 _write @ background.js:110 v @ background.js:116 (anonymous) @ background.js:116 b.write @ background.js:116 m @ background.js:116 h @ background.js:34 a.emit @ background.js:34 _ @ background.js:116 w @ background.js:116 v.push @ background.js:116 _onMessage @ background.js:80 (anonymous) @ background.js:80

Import works, but this is not ok :)

sebastiank9 · 2021-02-19T15:06:13Z

Also having the same problem.

Lost access to my Metamask-wallet and I can't import account via my json-file. Metamask gets stuck and crashes everytime. I have no seed phrase available though. Is there any way to recover? ... it's getting frustrating

I tried to recover with vault encryptor, but since the vault encryptor only saves the data from the last mnenomic wallet active on the browser, there is no way to recover older ones - or is that so?

Deepcryptodive · 2021-02-19T15:42:16Z

@sebastiank9 you should be able to import the json file into another wallet like MEW. It is less secure though.

https://kb.myetherwallet.com/en/getting-started/how-to-access-your-wallet/

To connect with Keystore/JSON + Password:
This is not a recommended way to connect. We highly suggest using MEW offline for this option.
Step 1. On the MEW front page, select ‘Access My Wallet’.

Step 2. Choose the ‘Software’ option to connect, then select ‘JSON File’ and click ‘Continue’.

Step 3. Locate your Keystore/JSON file in the pop-up window. It should begin with ‘UTC–’.

Step 4. Enter your password, and click ‘Unlock wallet’.

Step 5. You’re done!

adamsoffer · 2021-02-25T02:37:22Z

Any update on this issue?

mohsenghajar · 2021-03-01T12:47:02Z

I had the same issue yesterday on my desktop. But it worked on my laptop after about 5 minutes of it appearing frozen. Desktop has not worked yet.

Edit: it worked on my desktop too. Took about 10 minutes.

bhelm · 2021-03-08T08:18:43Z

Took long enough to google up and read this issue, but importing finished quickly after that (like 6 minutes). So be patient.
That was on a i7-7700HQ notebook. I guess import speed depends on CPU power available.

CyberPunkMetalHead · 2022-04-03T10:19:14Z

Still happening on Windows 10 and Google Chrome while importing a .json file generated by brownie-eth

fadyanwar · 2022-09-21T20:27:56Z

Yep, still happenings on Chrome running on Ubuntu

rolandsaven · 2022-10-05T20:48:06Z

Same here, incredibly slow to import from keystore - takes about 5 minutes but eventually imports it.

Chrome - Version 105.0.5195.125 (Official Build) (x86_64)
MacOS - 12.2.1 (21D62)
MetaMask - 10.19.0

github-actions · 2023-07-24T10:45:01Z

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.

shoenseiwaso · 2023-07-24T10:47:36Z

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.

Still a problem

shoenseiwaso · 2023-07-24T10:47:48Z

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.

Still a problem

haidarabdillah · 2023-07-25T16:31:15Z

still on problem

github-actions · 2023-12-03T00:17:16Z

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.

shoenseiwaso · 2023-12-03T13:09:56Z

Fairly certain this is still an issue.

github-actions · 2024-03-02T16:04:42Z

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.

miki-bgd-011 · 2024-03-02T16:07:44Z

What a shit show, 4y old bug. Switched to Rabby Wallet couple of months ago, oh boy what a difference!!

github-actions · 2024-07-11T20:05:13Z

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.

shoenseiwaso · 2024-07-11T23:19:42Z

Still an issue

github-actions · 2024-10-10T00:19:36Z

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.

shoenseiwaso · 2024-10-10T02:47:53Z

Still an issue

rekmarks added Sev2-normal Normal severity; minor loss of service or inconvenience. needs-reproduction type-bug labels Dec 22, 2020

mohamedmansour mentioned this issue Dec 23, 2020

MetaMask Freezing on 8.1.9 #10114

Closed

rekmarks mentioned this issue Jan 8, 2021

Metamask freezing in Firefox and v8.1.6-8.1.9 #10097

Closed

rekmarks removed the needs-reproduction label Jan 18, 2021

danjm assigned ryanml Mar 4, 2021

kantaroso mentioned this issue Jun 18, 2022

環境構築 kantaroso/dapps-app-sample#1

Closed

5 tasks

Gudahtt added the area-performance Issues relating to slowness of app, cpu usage, and/or blank screens. label Jul 20, 2022

danjm unassigned ryanml Nov 1, 2022

HowardBraham mentioned this issue Feb 15, 2023

Upgrading the Import Account modal #17763

Merged

github-actions bot added the stale issues and PRs marked as stale label Jul 24, 2023

github-actions bot removed the stale issues and PRs marked as stale label Sep 4, 2023

github-actions bot added the stale issues and PRs marked as stale label Dec 3, 2023

github-actions bot removed the stale issues and PRs marked as stale label Dec 3, 2023

github-actions bot added the stale issues and PRs marked as stale label Mar 2, 2024

github-actions bot removed the stale issues and PRs marked as stale label Mar 2, 2024

gauthierpetetin added the team-accounts label Apr 12, 2024

github-actions bot added the stale issues and PRs marked as stale label Jul 11, 2024

github-actions bot removed the stale issues and PRs marked as stale label Jul 12, 2024

github-actions bot added the stale issues and PRs marked as stale label Oct 10, 2024

github-actions bot removed the stale issues and PRs marked as stale label Oct 10, 2024

Version 8.1.9 freezes while importing keystore #10113

Version 8.1.9 freezes while importing keystore #10113

Comments

eiabea commented Dec 19, 2020

tmashuang commented Dec 19, 2020

eiabea commented Dec 19, 2020

tmashuang commented Dec 19, 2020

eiabea commented Dec 20, 2020

shoenseiwaso commented Dec 23, 2020

adamsoffer commented Jan 1, 2021

miki-bgd-011 commented Jan 2, 2021

davidgamero commented Jan 5, 2021

kyrogue commented Jan 6, 2021

rekmarks commented Jan 6, 2021

davidgamero commented Jan 6, 2021

rekmarks commented Jan 6, 2021

Deepcryptodive commented Jan 17, 2021 • edited Loading

d3v0n-m commented Jan 17, 2021

rekmarks commented Jan 18, 2021

eordano commented Jan 29, 2021

rekmarks commented Feb 2, 2021

honsa commented Feb 15, 2021 • edited Loading

sebastiank9 commented Feb 19, 2021 • edited Loading

Deepcryptodive commented Feb 19, 2021

adamsoffer commented Feb 25, 2021

mohsenghajar commented Mar 1, 2021 • edited Loading

bhelm commented Mar 8, 2021 • edited Loading

CyberPunkMetalHead commented Apr 3, 2022

fadyanwar commented Sep 21, 2022

rolandsaven commented Oct 5, 2022 • edited Loading

github-actions bot commented Jul 24, 2023

shoenseiwaso commented Jul 24, 2023

shoenseiwaso commented Jul 24, 2023

haidarabdillah commented Jul 25, 2023

github-actions bot commented Dec 3, 2023

shoenseiwaso commented Dec 3, 2023

github-actions bot commented Mar 2, 2024

miki-bgd-011 commented Mar 2, 2024

github-actions bot commented Jul 11, 2024

shoenseiwaso commented Jul 11, 2024

github-actions bot commented Oct 10, 2024

shoenseiwaso commented Oct 10, 2024

Deepcryptodive commented Jan 17, 2021 •

edited

Loading

honsa commented Feb 15, 2021 •

edited

Loading

sebastiank9 commented Feb 19, 2021 •

edited

Loading

mohsenghajar commented Mar 1, 2021 •

edited

Loading

bhelm commented Mar 8, 2021 •

edited

Loading

rolandsaven commented Oct 5, 2022 •

edited

Loading