Skip to content
This repository was archived by the owner on Jul 17, 2023. It is now read-only.
This repository was archived by the owner on Jul 17, 2023. It is now read-only.

Memory leaks if try to unblind a lot of utxos in FetchAndUnblindUtxos #32

Description

@louisinger

Step to reproduce:

  • run the tests a lot of time without resetting nigiri instance (~ 25 times for me)
  • now the tests accounts have a lot of UTXOS (~ 120)
  • yarn test fails: "Failed: "abort("Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0 "). Build with -s ASSERTIONS=1 for more info."

---> This is probably due to the secp256k-zkp WASM version.

Activity

  1. tiero commented on Feb 18, 2021

    @tiero
    Member

    I investigated a bit, seems to the fact that in the JS bindings are creatign this leak how they are written.

    This may be similar https://stackoverflow.com/questions/55884378/why-in-webassembly-does-allow-memory-growth-1-fail-while-total-memory-512mb-succ

  2. tiero commented on Feb 22, 2021

    @tiero
    Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions