Critiques pour MetaMask – Crypto Wallet
MetaMask – Crypto Wallet par MetaMask
568 notes
- Noté 1 sur 5par 企业号, il y a 4 ans
- Noté 1 sur 5par animefan333, il y a 4 ansnever installed this . found it because firefox was using not 1.4gb ram and 5%-28% cpu usage to 95% using over 5gb and 6 process of 750mb to 900mb each. after removing this metamask ram usage went back to 1.4gb and cpu usage went back to 5%-28% . firefox needs to remove this.
- Noté 1 sur 5par Reggie, il y a 4 ans
- Noté 1 sur 5par ccl, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17670026 de Firefox, il y a 4 anstracking IP's isn't going to get you far
- Noté 1 sur 5par Utilisateur ou utilisatrice 17429829 de Firefox, il y a 4 ansI am using a Dell Laptop with windows 11 and something corrupted Firefox browser with the Metamask add on. I got help to get firefox working and the tech had me delete items I thought were totally unrelated to Metamask and they got firefox working. But now Metamask does not stop to allow me to use my pass word. Now Metamask goes straight to a page to start a new wallet or to use the 12 word pass code. That does not work either. Now was it a firefox browser problem or Metamask. In any case I have some crypto in that wallet that I can not access........yet?
- Noté 1 sur 5par karlpopper, il y a 4 ansThis has been working great until Firefox 107 (Mac OS Catalina). Now, as another user also observed, it has a massive memory leak that eats up all the RAM, loads the CPU, and eventually crashes the machine. I really hope my comment is seen and this gets fixed soon. Other than that, it's been great and mostly reliable. It did crash and fail to load about a year ago and I had to manually re-add all of my wallets and tokens again, but hopefully that won't happen again.
- Noté 1 sur 5par badr, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 15569291 de Firefox, il y a 4 ansAfter the latest update I had to remove the extension because it is using very quickly all the RAM and the browser does not work anymore. I spent quite a lot of time understanding what was going on and I finally tracked the issue to this extension using about:performance
- Noté 1 sur 5par Utilisateur ou utilisatrice 17582103 de Firefox, il y a 4 ans
- Noté 1 sur 5par oldguy, il y a 4 ans
- Noté 1 sur 5par Dip, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17587132 de Firefox, il y a 4 ans
- Noté 1 sur 5par Silver, il y a 4 ans
- Noté 1 sur 5par AmirMahdi, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17548025 de Firefox, il y a 4 ans
- Noté 1 sur 5par My Dung, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17155808 de Firefox, il y a 4 ans
- Noté 1 sur 5par Favvy, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17516329 de Firefox, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17492994 de Firefox, il y a 4 ans
- Noté 1 sur 5par Utilisateur ou utilisatrice 17490556 de Firefox, il y a 4 ans