AugurProject / augur-app

Augur Desktop Electron Application
MIT License
222 stars 22 forks source link

[BUG] Illegal instruction when syncing #495

Open enolan opened 4 years ago

enolan commented 4 years ago

Summary

The daemon crashes when syncing, reporting an illegal instruction. Restarting works, and it continues the sync process for a while before crashing again.

Steps to reproduce

  1. Download the AppImage.
  2. Run it, syncing using a local (full) Parity node.

Expected behavior

Should sync without error

Screenshots

End of log:

[10:17:27.275] [info] Processing 1 logs
Fetched 10 / 45 block details (current: 7747189)
Fetched 20 / 45 block details (current: 7747274)
[10:17:29.925] [info] new block: 6263560, 1535966044 (Mon Sep 03 2018 02:14:04 GMT-0700 (PDT))
Fetched 30 / 45 block details (current: 7747472)

<--- Last few GCs --->

[23225:0x2b05d3e95000]   702457 ms: Mark-sweep 1973.9 (2083.0) -> 1973.8 (2083.0) MB, 1614.2 / 0.0 ms  allocation failure GC in old space requested
[23225:0x2b05d3e95000]   704098 ms: Mark-sweep 1973.8 (2083.0) -> 1973.9 (2080.0) MB, 1641.4 / 0.0 ms  last resort GC in old space requested
[23225:0x2b05d3e95000]   705184 ms: Mark-sweep 1973.9 (2080.0) -> 1973.9 (2080.0) MB, 1085.5 / 0.0 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0xbc96518427d]
    1: StubFrame [pc: 0xbc965c07ec1]
Security context: 0xc68a9325709 <JSObject>
    2: new constructor(aka Request) [/home/enolan/.cache/appimage-run/4b050d6c776ad1af3cb6bda709df9b863e896ba98d8c5a5c4275f127c9a90a7a/squashfs-root/resources/app.asar/node_modules/request/request.js:123] [bytecode=0x2382722e719 offset=171](this=0x1003a2a7f099 <Request map = 0x2832fc2568f1>,options=0x27c4d7dff281 <Object ma...

Illegal instruction (core dumped)

Full log here: log.log

Environment

If using Augur App:
enolan commented 4 years ago

Core dump file. It's actually an lz4 compressed file, I had to rename it to .zip to get GitHub to let me upload it. core.chrootenv.1000.57dec26905a942c0aad25fe2ac1a638c.23823.1580582007000000000000.zip

pgebheim commented 4 years ago

This error is due to running into nodejs's heap limits. In order to fix it it would need to run this process with a higher "max_old_space_size"...

If you're running in an environment where you can easily set the environment variables for when the app loads, try NODE_OPTIONS="--max_old_space_size=6144"