Coder Social home page Coder Social logo

madebythepinshub / dogehouse-electron-app-snap Goto Github PK

View Code? Open in Web Editor NEW
2.0 2.0 0.0 114 KB

DogeHouse Electron client app ported as an Snap. See https://github.com/benawad/dogehouse/issues/575 for details.

License: MIT License

Shell 100.00%

dogehouse-electron-app-snap's People

Contributors

ajhalili2006 avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

dogehouse-electron-app-snap's Issues

snapcraft-build/iohook-install: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Details

  • Is error reproducible in local dev machine? Probably not.
  • Is this happened in either GitLab CI or Snapcraft Builds powered by Launchpad.net? GitLab CI

CI Logs

Pardon the misspelling you'll found in the snap/snapcraft.yaml file. See https://gitlab.com/MadeByThePinsHub/snapcrafters/dogehouse/-/jobs/1111920586 for the full logs.

+ echo ==> Inlnstalling build dependencies...
==> Inlnstalling build dependencies...
+ npm install
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
npm WARN lifecycle The node binary used for scripts is /snap/bin/node but npm is using /snap/node/3790/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
> [email protected] install /data/parts/dogehouse/build/baklava/node_modules/iohook
> node install.js
node 83 win32 x64
Downloading prebuild for platform: iohook-v0.7.2-node-v83-win32-x64
... and 1 more
<--- Last few GCs --->
[4702:0x4a57a60]    35915 ms: Mark-sweep (reduce) 1849.0 (1851.9) -> 1849.0 (1853.9) MB, 4279.1 / 0.0 ms  (average mu = 0.102, current mu = 0.000) allocation failure scavenge might not succeed
[4702:0x4a57a60]    40181 ms: Mark-sweep (reduce) 1850.0 (1855.9) -> 1850.0 (1856.9) MB, 4265.8 / 0.0 ms  (average mu = 0.054, current mu = 0.000) allocation failure scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xa1a470 node::Abort() [/snap/node/3790/bin/node]
 2: 0xa1a8c8 node::OnFatalError(char const*, char const*) [/snap/node/3790/bin/node]
 3: 0xba97ee v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/snap/node/3790/bin/node]
 4: 0xba9b77 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/snap/node/3790/bin/node]
 5: 0xd8e045  [/snap/node/3790/bin/node]
 6: 0xd8eee6 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/snap/node/3790/bin/node]
 7: 0xd9d80c v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/snap/node/3790/bin/node]
 8: 0xd9e0dc v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/snap/node/3790/bin/node]
 9: 0xda18fc v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/snap/node/3790/bin/node]
10: 0xd7263d v8::internal::HeapObject v8::internal::Heap::AllocateRawWith<(v8::internal::Heap::AllocationRetryMode)1>(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/snap/node/3790/bin/node]
11: 0xd7267b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/snap/node/3790/bin/node]
12: 0x10e8f84 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/snap/node/3790/bin/node]
13: 0x14ce419  [/snap/node/3790/bin/node]
Aborted (core dumped)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/dmg-license):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] install: `node install.js`
npm ERR! Exit status 134
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-19T11_35_15_107Z-debug.log
Failed to run 'override-build': Exit code was 134.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.