LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-02-2018, 02:19 PM   #1
glupa4e
Member
 
Registered: Jan 2011
Posts: 248

Rep: Reputation: 2
Atom Installation - FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory


Hello,
tried to install the Atom text editor. I did that via sboui (sbopkg). The two build options i set:
Code:
DISABLE_METRICS=yes
DELETE_CACHE=yes
I have already the package Electron installed. Here is som output of the log:
Code:
==== JS stack trace =========================================

Security context: 0x35b0cfa3fa99 <JS Object>
    2: parse [/tmp/SBo/atom-1.23.3/script/node_modules/tello/node_modules/atomdoc/lib/parser.js:~29] [pc=0x38cffbb3ab7a] (this=0x8fd853da1c9 <an Object wit$
    3: docFromDocString [/tmp/SBo/atom-1.23.3/script/node_modules/tello/lib/digester.js:187] [pc=0x38cffba1a145] (this=0x1c3dfe59879 <a Digester with map 0$

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0xe16b2c [node]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [node]
 6: v8::internal::Runtime_AllocateInTargetSpace(int, v8::internal::Object**, v8::internal::Isolate*) [node]
 7: 0x38cff82062bf
atom.SlackBuild.build: line 104:  3432 Aborted                 npm_config_arch=$NPMARCH npm_config_target_arch=$NPMARCH PYTHON=python2 ./script/build
Could you help me fix that error?
I have recently done upgrade of my Slackware 14.2 x64 installation with multilib support.
 
Old 05-02-2018, 04:57 PM   #2
keefaz
LQ Guru
 
Registered: Mar 2004
Distribution: Slackware
Posts: 6,230

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
Quote:
Atom may failed to build at first attempt.
Simply retry the process and it should be working.
https://slackbuilds.org/repository/1...elopment/atom/

May try a new execution of the Slackbuild or sboinstall...
 
Old 05-04-2018, 11:07 AM   #3
glupa4e
Member
 
Registered: Jan 2011
Posts: 248

Original Poster
Rep: Reputation: 2
2 Times failure

At the beginning i did the installation via sbopkg (sboui).

This time i downloaded the SlackBuild and run the command 2 times as root:
Code:
DISABLE_METRICS=yes DELETE_CACHE=yes ./atom.SlackBuild

Both times i had the following error:
Code:
Wrote Dependencies Fingerprint: /tmp/SBo/atom-1.23.3/node_modules/.dependencies-fingerprint b81558bc5df096d7e324138f418faed77dda136a
Copying assets to /tmp/SBo/atom-1.23.3/out/app
Transpiling packages with custom transpiler configurations in /tmp/SBo/atom-1.23.3/out/app
 transpiling for package github
Installing modules ✓
Transpiling Babel paths in /tmp/SBo/atom-1.23.3/out/app
Transpiling CoffeeScript paths in /tmp/SBo/atom-1.23.3/out/app
Transpiling CSON paths in /tmp/SBo/atom-1.23.3/out/app
Transpiling PEG.js paths in /tmp/SBo/atom-1.23.3/out/app
Generating module cache for /tmp/SBo/atom-1.23.3/out/app
Generating pre-built less cache in /tmp/SBo/atom-1.23.3/out/app/less-compile-cache
Generating metadata for /tmp/SBo/atom-1.23.3/out/app/package.json
Generating API docs at /tmp/SBo/atom-1.23.3/docs/output/atom-api.json

<--- Last few GCs --->

 1180947 ms: Mark-sweep 1375.7 (1404.8) -> 1377.5 (1404.8) MB, 705.4 / 0.0 ms [allocation failure] [GC in old space requested].
 1181738 ms: Mark-sweep 1377.5 (1404.8) -> 1379.3 (1404.8) MB, 710.3 / 0.0 ms [allocation failure] [GC in old space requested].
 1182530 ms: Mark-sweep 1379.3 (1404.8) -> 1381.6 (1403.8) MB, 710.5 / 0.0 ms [last resort gc].
 1183314 ms: Mark-sweep 1381.6 (1403.8) -> 1383.8 (1403.8) MB, 784.3 / 0.0 ms [last resort gc].


<--- JS stacktrace --->

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

Security context: 0x7faabb3fa99 <JS Object>
    2: parse [/tmp/SBo/atom-1.23.3/script/node_modules/tello/node_modules/atomdoc/lib/parser.js:~29] [pc=0xe37710e0bfa] (this=0x17fbb57da149 <an Object with map 0x3a17daf8dd19>,docString=0x7faabb04241 <undefined>)
    3: docFromDocString [/tmp/SBo/atom-1.23.3/script/node_modules/tello/lib/digester.js:187] [pc=0xe3772c0b405] (this=0x5e12a534981 <a Digester with map 0xf9e608060f1>,docString=0x1573...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0xe16b2c [node]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [node]
 6: v8::internal::Runtime_AllocateInTargetSpace(int, v8::internal::Object**, v8::internal::Isolate*) [node]
 7: 0xe37708062bf
./atom.SlackBuild: line 104:  9841 Aborted                 npm_config_arch=$NPMARCH npm_config_target_arch=$NPMARCH PYTHON=python2 ./script/build
 
Old 05-28-2018, 10:19 PM   #4
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,442

Rep: Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069
FWIW, I was not successful building atom here either. I'm not sure if I got farther than you or not, but for me, it used up all my memory and swap (12G total!) while generating the doc API or something like that. I ended up just installing the binary version, atom-amd64, instead. It is more up-to-date anyway.

EDIT: I didn't read closely enough - looks like we are getting the same error. Anyway, seems to be documented in this issue on Github:

https://github.com/atom/atom/issues/16777

This issue was raised and closed after the 1.23.3 release, which makes me think that simply updating to a newer version would solve the problem.

Last edited by montagdude; 05-28-2018 at 11:06 PM.
 
1 members found this post helpful.
Old 05-29-2018, 01:29 AM   #5
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740
download vscode and run it. no build required.
I do not know why Atom thinks it needs to be build. pulling in a lot of nodejs stuff as root is for sure the last thing I do
also, tried Atom, but changed to code because for what I do it works much better and is more stable
 
Old 06-03-2018, 03:32 PM   #6
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,442

Rep: Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069
Quote:
Originally Posted by montagdude View Post
This issue was raised and closed after the 1.23.3 release, which makes me think that simply updating to a newer version would solve the problem.
As suspected, 1.27.2 with no problems. Just replace the version number in atom.SlackBuild and download the correct source file. I will email the maintainer on SBo to request an update.
 
Old 06-08-2018, 11:26 AM   #7
glupa4e
Member
 
Registered: Jan 2011
Posts: 248

Original Poster
Rep: Reputation: 2
Thanks montagdude, i was able to install the verrsion https://github.com/atom/atom/releases/tag/v1.27.0 from slackbuilds.org. Now i have atom-am64.

I also installed vscode to take a look at it.

Last edited by glupa4e; 06-08-2018 at 11:35 AM.
 
Old 06-08-2018, 09:10 PM   #8
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,442

Rep: Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069
Quote:
Originally Posted by glupa4e View Post
Thanks montagdude, i was able to install the verrsion https://github.com/atom/atom/releases/tag/v1.27.0 from slackbuilds.org. Now i have atom-am64.

I also installed vscode to take a look at it.
That was my experience too, and I could never get 1.23.3 to build. But when I brought it up on the mailing list, Willy said that 1.27.2 had the same problem building as 1.23.3, but attempting the build a second time was successful. So I don't really know what's going on there. I guess I should test on a clean VM, but I've kind of lost motivation because I decided that tmux + vim + ctags is a better development environment for me than Atom or any other IDE-lite or IDE anyway.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Debugging memory allocation issues using glibc only - heap consistency checks LXer Syndicated Linux News 0 03-16-2017 02:33 AM
savebase memory allocation failed during boot up vathsan AIX 1 02-23-2009 02:41 AM
Random restarts, and possible memory leak (0-order allocation failed (gfp=0x1d2/0) ) rose_bud4201 Linux - Kernel 2 07-30-2007 10:02 AM
memory allocation error l00zer Linux - Software 2 09-09-2005 10:43 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration