Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling multiple Send() fns on txmgr.go in succession produces a SIGSEGV on trx.Hash() in error handler for RawTransact() #126

Open
vanderian opened this issue Feb 23, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@vanderian
Copy link

Describe the bug
Sending multiple trx in quick succession ends up with one of them failing due to nonce too low.
Error handler outputs the error message with associated trx.Hash(), which fails with SIGSEGV.
Removing the hash from err message "fixed" the crash.

To Reproduce
Duplicate the line in code which sends a trx, ending up with two simultaneous trxs with one failing with 'nonce too low' and producing the crash

Expected behavior
Does not crash

OS details

  • OS: Mac/m1

Additional context
Fixed on a fork by adding a mutex to allow only one in flight trx, and fetching a new nonce
master...mangata-finance:eigensdk-go:feature/expired-responses#diff-223616ebe949cff704b8d355a461951d12ccf06b07d593d9983879d1735bf140

@vanderian vanderian added the bug Something isn't working label Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant