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

selfdestruct NPE #1104

Closed
letypequividelespoubelles opened this issue Sep 5, 2024 · 6 comments
Closed

selfdestruct NPE #1104

letypequividelespoubelles opened this issue Sep 5, 2024 · 6 comments
Assignees
Labels
bug Something isn't working ranges

Comments

@letypequividelespoubelles
Copy link
Collaborator

letypequividelespoubelles commented Sep 5, 2024

Blocks

8043758
8019521
8005327

Issues

          three more blocks:

blockNumber=8043758
07:20:19.171 [vert.x-worker-thread-19] ERROR org.hyperledger.besu.ethereum.api.query.BlockchainQueries - failed worldstate query for 0x71a447a9891baead07ec1dae958a3d283a9d820ebd2421820ba567c708be4a6b
net.consensys.linea.zktracer.ZkTracer$TracingExceptions: Exceptions triggered while tracing:

  • Cannot invoke "net.consensys.linea.zktracer.module.hub.AccountSnapshot.deepCopy()" because "this.selfdestructorAccountAfter" is null

  • Cannot invoke "net.consensys.linea.zktracer.module.hub.AccountSnapshot.deepCopy()" because "this.selfdestructorAccountAfter" is null

    at net.consensys.linea.zktracer.ZkTracer.traceEndConflation(ZkTracer.java:184) ~[?:?]
    at org.hyperledger.besu.services.TraceServiceImpl.lambda$trace$3(TraceServiceImpl.java:166) ~[besu-24.8-develop-dce796c.jar:24.8-develop-dce796c]
    at org.hyperledger.besu.ethereum.api.jsonrpc.internal.processor.Tracer.lambda$processTracing$0(Tracer.java:51) ~[besu-api-24.8-develop-dce796c.jar:24.8-develop-dce796c]
    

blockNumber=8019521:

7:20:14.436 [vert.x-worker-thread-7] ERROR org.hyperledger.besu.ethereum.api.query.BlockchainQueries - failed worldstate query for 0x6ffd55ddcfe84c049ff61fa1e33acf275d3eac3d17b8c1ac92b479231efa639f
net.consensys.linea.zktracer.ZkTracer$TracingExceptions: Exceptions triggered while tracing:

  • Insufficient balance
    Address: 0xf2614a233c7c3e7f08b1f887ba133a13f1eb2c55
    Balance: 0x0000000000000000000000000000000000000000000000000000000000000000
    Value: 0x00000000000000000000000000000000000000000000000000e0241f2da18713

    at net.consensys.linea.zktracer.ZkTracer.traceEndConflation(ZkTracer.java:184) ~[?:?]
    at org.hyperledger.besu.services.TraceServiceImpl.lambda$trace$3(TraceServiceImpl.java:166) ~[besu-24.8-develop-dce796c.jar:24.8-develop-dce796c]
    at org.hyperledger.besu.ethereum.api.jsonrpc.internal.processor.Tracer.lambda$processTracing$0(Tracer.java:51) ~[besu-api-24.8-develop-dce796c.jar:24.8-develop-dce796c]
    at org.hyperledger.besu.ethereum.api.query.BlockchainQueries.lambda$getAndMapWorldState$24(BlockchainQueries.java:950) ~[besu-api-24.8-develop-dce796c.jar:24.8-develop-dce796c]
    at java.base/java.util.Optional.flatMap(Optional.java:289) ~[?:?]
    

blockNumber=8005327:

java.lang.IllegalArgumentException: null
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:129) ~[guava-33.0.0-jre.jar:?]
at net.consensys.linea.zktracer.module.hub.Hub.exitDeploymentFromDeploymentInfoPov(Hub.java:725) ~[?:?]
at net.consensys.linea.zktracer.module.hub.Hub.traceContextExit(Hub.java:662) ~[?:?]

Originally posted by @FlorianHuc in #1090 (comment)

@letypequividelespoubelles
Copy link
Collaborator Author

maybe already fixed as a355f8c has been merged after the release

@OlivierBBB
Copy link
Collaborator

Are these 3 individual blocks failing ? Could you put this issue in the conventional format please @letypequividelespoubelles ?

@lorenzogentile404
Copy link
Collaborator

8005327 is solved. The other 2 still needs debugging.

@lorenzogentile404
Copy link
Collaborator

8043758 is solved too.

@lorenzogentile404 lorenzogentile404 linked a pull request Sep 5, 2024 that will close this issue
@letypequividelespoubelles
Copy link
Collaborator Author

Are these 3 individual blocks failing ? Could you put this issue in the conventional format please @letypequividelespoubelles ?

I didn't take a look, I just copy paste #1090 (comment)

@OlivierBBB
Copy link
Collaborator

Could you still put it conventional form please @letypequividelespoubelles ?

@letypequividelespoubelles letypequividelespoubelles closed this as not planned Won't fix, can't repro, duplicate, stale Oct 8, 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 ranges
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants