You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the createToken action is submitted, the WebSocket server hangs and stops responding. There are no errors in the logs, and the action itself is executed successfully. However, all WebSocket connections to the node freeze after this action.
Transfer transactions work correctly through WebSocket without any issues.
The issue happens consistently after every createToken action.
The problem is not related to the client. The same behavior occurs when listening for new blocks in Go, suggesting that the WebSocket server itself hangs, though it's unclear if block production stops or if it's solely a WebSocket issue.
User get's charged gas fees, so looks like Tx is being processed
Additional Information:
Aaron's suggestion: This issue could be related to the pubsub package used by the WebSocket server. Possible problematic areas include message_buffer.go#L124 and message_buffer.go#L116, where a deadlock might occur.
The text was updated successfully, but these errors were encountered:
When the
createToken
action is submitted, the WebSocket server hangs and stops responding. There are no errors in the logs, and the action itself is executed successfully. However, all WebSocket connections to the node freeze after this action.Source Code:
createToken
action source: create_token.goDetails:
createToken
action.Additional Information:
pubsub
package used by the WebSocket server. Possible problematic areas include message_buffer.go#L124 and message_buffer.go#L116, where a deadlock might occur.The text was updated successfully, but these errors were encountered: