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.

Sign up for GitHub

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

Jump to bottom

GetEpochInformation can freeze the OS #84

Open
wqking opened this issue Aug 30, 2019 · 1 comment
Open

GetEpochInformation can freeze the OS #84

wqking opened this issue Aug 30, 2019 · 1 comment
Assignees
@meyer9
Labels
beacon bug Something isn't working

Comments

@wqking
Copy link
Contributor

wqking commented Aug 30, 2019

Reproduce:

  1. Create a EpochInformationRequest.
  2. Set EpochInformationRequest.EpochIndex to very large number (tested 10000000).
  3. Call a Beacon node's GetEpochInformation with the request.

The Beacon node will eat up all RAM and freeze the OS.
@wqking wqking added beacon bug Something isn't working labels Aug 30, 2019
@meyer9
Copy link
Member

meyer9 commented Sep 1, 2019

We should set a limit on how far ahead to simulate empty blocks (probably around 1-2 epochs). If it requests more than that, we should return that there is no epoch information currently (needs to be synced up with the network).

@meyer9 meyer9 self-assigned this Sep 1, 2019
@meyer9 meyer9 changed the title Beacon RPC bug -- GetEpochInformation can freeze the OS GetEpochInformation can freeze the OS Sep 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@meyer9 meyer9

Labels
beacon bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@meyer9 @wqking