Skip to content
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.

CreationCode makes ethermintd exploded #308

Closed
FrancoCRO opened this issue Jul 16, 2021 · 14 comments
Closed

CreationCode makes ethermintd exploded #308

FrancoCRO opened this issue Jul 16, 2021 · 14 comments
Assignees

Comments

@FrancoCRO
Copy link

FrancoCRO commented Jul 16, 2021

System info:

Max OS X
Main (d7c9656d7704e77ed0f71ea45755cadc25dbd979)

Steps to reproduce:

  1. Deploy CreationCode with the code below, using remix or any tool you like (https://gist.github.com/FrancoCRO/b198c1dc6d63626e92cd00f7fedd9406)
  2. Call CODE_HASH

Expected behavior:
Returns code hash

Actual behavior:
Ethermintd becomes unresponsive, and is crazy printing EVM stack logs for minutes, and you have to SIGKILL it

Additional info:
This CreationCode method is used by Uniswap-family swaps
The PancakePair contract code is obtained from here (https://bscscan.com/address/0x0eD7e52944161450477ee417DE9Cd3a859b14fD0#code)
And is called from here
(https://bscscan.com/address/0xcA143Ce32Fe78f1f7019d7d551a6402fC5350c73#code)

@FrancoCRO
Copy link
Author

Seems it will eventually returns a result, but it takes ... 1078 seconds.

{"output":"a70eeb9bb3b548bd3404057cd53405c892d49801acca673e77238beb06b75b15","gasUsed":"0xcb2e","time":1078131106396}

@leejw51crypto
Copy link
Contributor

nice catch

@fedekunze
Copy link
Contributor

Ethermintd becomes unresponsive, and is crazy printing EVM stack logs for minutes, and you have to SIGKILL it

you can run the node without the --trace flag to disable stack tracing

@leejw51crypto
Copy link
Contributor

seems recursive calls itself

@FrancoCRO
Copy link
Author

Yeah seems that with --trace turned off it returns result almost immediately. Thanks :D

@yijiasu-crypto
Copy link
Contributor

this is not bug just printing too much to stdio I think

@leejw51crypto
Copy link
Contributor

today i'll check this issue

@leejw51crypto leejw51crypto self-assigned this Jul 19, 2021
@leejw51crypto
Copy link
Contributor

this is not bug just printing too much to stdio I think

agree

@leejw51crypto
Copy link
Contributor

leejw51crypto commented Jul 19, 2021

i'll crosscheck it's legitimately processed in evm
i assume processing time is very long because of the printing output

@leejw51crypto
Copy link
Contributor

reproduced in metamask X remix

@leejw51crypto
Copy link
Contributor

modifying now

leejw51crypto added a commit to leejw51crypto/ethermint that referenced this issue Jul 19, 2021
@leejw51crypto
Copy link
Contributor

submitted pr, it's simple one ^^;

@thomas-nguy
Copy link
Contributor

should we close the issue?

@FrancoCRO
Copy link
Author

FrancoCRO commented Jul 22, 2021

should we close the issue?

I think yes, if the limitation is at the stdio side

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants