[Bug]: MetaMask stays loading indefinetly and get error `StreamProvider - Unknown response id for response: [object Object]` when doing *some* contract interactions

[seaona]

Describe the bug

Problem: when I call the function for mint an ERC1155 token, MetaMask stays loading indefinetly and I get the console error Error in event handler: Error: StreamProvider - Unknown response id for response: [object Object] .

mint-erc1155-streamprovider.mp4

This also happens when I call another contract function.

streamprovider-error.mp4

[EDITED] It seems the error could start whenever we deploy a contract. It's not 100% deterministic, so further investigation needs to be done.

Steps to reproduce [EDITED]

1. Go to Remix https://remix.ethereum.org/
2. Create a contract

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.17;

contract Fallback {
    event Log(string func, uint gas);
    fallback() external payable {
        emit Log("fallback", gasleft());
    }
    receive() external payable {
        emit Log("receive", gasleft());
    }
    function getBalance() public view returns (uint) {
        return address(this).balance;
    }
}

3. Deploy this contract on Goerli - see error on console // if not, deploy another contract
4. Create another contract

contract SendToFallback {
    uint val = 0;
    function transferToFallback(address payable _to) public payable {
        _to.transfer(msg.value);
    }

    function callFallback(address payable _to) public payable {
        (bool sent, ) = _to.call{value: msg.value}("");
        require(sent, "Failed to send Ether");
    }
    function count(uint _val) public {
        val = _val;
    }
}

6. Deploy this contract on Goerli - see error on console

After this, we are into a broken state, shown in the videos above.

Error messages or log output

No response

Version

develop [EDITED]

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

[wbt]

This looks like a duplicate of #17154 though this one has much more detail in the description, so it might be fair to close that one as a duplicate of this.
I am seeing the same issue on calls to custom contracts on a private network and even non-transaction signature requests.
In each case, the signature or transaction confirmation appears to go through just fine, but the interface remains with the forever-loading spinner and gray overlay indefinitely (tested >1 hour). Leaving DevTools open, after a bit over an hour and a half, I see "Paused before potential out-of-memory crash" on common-1.js:12 (part of regenerator-runtime);

Resuming does produce the out of memory crash, though the console doesn't show anything new:

To get to the next confirmation, you have to close out of MetaMask and ignore any "MetaMask Notification" popup window (because clicking X on that will be treated as a rejection), then re-open MetaMask from the button on the browser toolbar.
I'm also seeing high CPU usage due to an apparent bug in Windows Explorer, which slows down the computer performance somewhat and may make this bug more likely to be observed, but don't have any particular reason to think that's the cause.

[DimasikS12]

Hi! I have this problem too. Can you please tell me what is causing this error and how to solve it?

[wbt]

The cause is unclear; it appears to be a bug in MetaMask.

You can get a short term solution by clicking in some blank area in your browser, then clicking on the MetaMask pinned icon extension to get it to reload and hopefully display the next confirmation prompt, though it sometimes crashes then too (just keep trying). Do NOT click the X on the crashed "Metamask Notification" popup as this is treated as a signature rejection.

For the medium term, the only way to really solve it seems to be to use an alternative (see whatthefox.com as an example listing; no endorsement of their proposed alternative implied).

For a long term fix, someone will have to take a deep dive into MetaMask code, ideally after being able to reliably reproduce the issue. That's easier said than done though.

[DimasikS12]

I can reproduce this error, it occurs after running certain contract methods on my site. When calling certain functions on my site that call certain methods on my contract, this error appears in MetaMask. I think that this is not a problem in MetaMask, but in the contract method call

[wbt]

Do you have (or can you make) clear steps for reproduction that don't cost real-world money? (e.g. something on a test network).

[Samclay8]

I get this performing most actions. I have around 10 wallets in my metamask and simply switching between them presents me with this infinite loading issue. Extremely annoying and have resulted in performing my day to day activities on firefox rather than chrome whilst this persists. Has anyone found a fix?

[DimasikS12]

Do you only have this problem in Chrome browser?

[DimasikS12]

And please tell me which MacOS, Linux or Windows system do you use? It's just that I'm currently testing on Windows and don't see this error. By the way, if you have error, you can remove it. You just need to go to the MetaMask settings and reset the account, after that the error disappears.

[Samclay8]

Windows 11, chrome version 111.0.5563.65, metamask 10.25.0.

Yes the error is specific to chrome and unfortunately resetting account data does not remove the issue. I have reset the account, and even completely uninstalled and reinstalled and the issue persists.

[wbt]

I'm also seeing it on Windows 10 w/Chrome.

[DimasikS12]

Yes, that is right. This bug appeared in the latest version of MetaMask v10.25.0. I installed the previous version of MetaMask 10.24.2 and everything works fine. I also put debuggers in the MetaMask v10.25.0 code and noticed that when calling certain methods of my smart-controct, this error starts to appear, because MetaMask stops receiving id, as far as I understand, this is a store id, which is constantly generated. In general, this bug is due to updating MetaMask to version 10.25.0. The second screenshot shows that the id was not generated and it simply does not exist, although it should be.