We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
combineTransactionInfo
Large queries with many transactions can lead to:
<--- Last few GCs ---> 1999525 ms: Scavenge 1394.6 (1455.4) -> 1394.6 (1455.4) MB, 0.7 / 0 ms (+ 2.3 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep]. 2000193 ms: Mark-sweep 1394.6 (1455.4) -> 1394.1 (1455.4) MB, 668.1 / 0 ms (+ 3.2 ms in 2 steps since start of marking, biggest step 2.3 ms) [last resort gc]. 2000854 ms: Mark-sweep 1394.1 (1455.4) -> 1394.4 (1455.4) MB, 661.1 / 0 ms [last resort gc]. <--- JS stacktrace ---> ==== JS stack trace ========================================= Security context: 0x34a381c37399 <JS Object> 1: combineTransactionInfo [/home/testuser/bitcore-node/lib/services/address/history.js:~122] [pc=0x16517e689647] (this=0x3235e0570389 <an AddressHistory with map 0x2681979dc3d1>) 2: /* anonymous */ [/home/testuser/bitcore-node/lib/services/address/history.js:49] [pc=0x16517e64dd8a] (this=0x34a381cb7909 <JS Global Object>,err=0x34a381c04111 <null>) 4: /* anonymous */ [/home/testuser/bit... FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory Aborted (core dumped)
The text was updated successfully, but these errors were encountered:
Was converted to use streams.
Sorry, something went wrong.
No branches or pull requests
Large queries with many transactions can lead to:
The text was updated successfully, but these errors were encountered: