472 reviews
- Rated 1 out of 5by Firefox user 17251632, 2 years ago
- Rated 1 out of 5by Firefox user 17722643, 2 years ago
- Rated 1 out of 5by Firefox user 17691757, 2 years ago
- Rated 1 out of 5by 企业号, 2 years ago
- Rated 1 out of 5by animefan333, 2 years agonever 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.
- Rated 1 out of 5by Reggie, 2 years ago
- Rated 1 out of 5by ccl, 2 years ago
- Rated 1 out of 5by Firefox user 17429829, 2 years agoI 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?
- Rated 1 out of 5by karlpopper, 2 years agoThis 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.
- Rated 1 out of 5by badr, 2 years ago
- Rated 1 out of 5by Firefox user 15569291, 2 years agoAfter 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
- Rated 1 out of 5by Firefox user 17582103, 2 years ago
- Rated 1 out of 5by oldguy, 2 years ago
- Rated 1 out of 5by Dip, 2 years ago
- Rated 1 out of 5by Firefox user 17587132, 2 years ago
- Rated 1 out of 5by Silver, 2 years ago
- Rated 1 out of 5by AmirMahdi, 2 years ago
- Rated 1 out of 5by Firefox user 17548025, 2 years ago
- Rated 1 out of 5by My Dung, 2 years ago
- Rated 1 out of 5by Firefox user 17155808, 2 years ago
- Rated 1 out of 5by Favvy, 2 years ago