This is related to the multiple issuance of an asset in Multichain. I have faced the issue multiple times where in the nodes wallets failed to respond after a particular state of the system. It took me some time to pin point the issue. Once the issue is reached, the multichain nodes fails to respond and goes to hang state which doesn't get solved using reindex=1 as well.
If an asset is issued with open as true. If the asset is issued 6 -7 times further and the command listassets assetname is executed, wallet hangs. The pattern remain same if the address balances is fetched. I have multiple chains with the issue. If required I can share the data.
The issue is not related to the number of assets in the chain but the number of times any asset is reissued. I have tested creation of 600-700 assets and listing them successfully. The issue can be reproduced by the following process:
- Create a new chain
- Issue an asset to the origin address
- Wait for the asset to get confirmed by checking for the asset reference name in listassets assetname
- Execute listasset assetname true
- Reissue the asset
- Execute listassets assetname true/false or listassets or listassets '' true
- Repeat 5 and 6 till the commands fails to respond.
One the system hangs. We can kill the process and restart multichain. The getinfo commands work, the moment commands like gettotalbalances or listassets is executed, it will go to hang state. I think the issue is related to fixed memory size allocation in the code programme.
Let me know if you require more info.