Arch Linux

blackholeneo

Member

Registered: 2024-07-29

Posts: 3

[solved] Compiling V8 from AUR - can't compile and exit terminal

Hi everyone,

This is my first post in the Arch forums, and English is not my first language (sorry for any grammar mistakes). I've been using Arch for 6 months, and last week I installed it on my everyday laptop. Everything is great, but I have this problem.

I use R for my statistical work. While installing packages, I got an error because the V8 library doesn't seem to be installed on the system. So, I went to install it from AUR. There are two main versions, v8 and v8-r. The latter works better in R (according to the GitHub page of the V8 package for R). But every time I try to install it, the PC freezes after 2 hours of compilation. I downloaded the repo and compiled it with makepkg, but the problem appears again. While compiling, the RAM and CPU usage elevates to 100%. When it crashes, the entire system freezes.

PC specs: Asus Vivobook S433 with Intel Core i7-1165G7 @ 2.80GHz, 8 GB RAM, 1 TB SSD. Kernel 6.6.42-1-lts, running KDE Plasma 6.1.3 on Wayland.

I asked ChatGPT for solutions, but I want to read the opinions of the community as well.

Thanks for your help.

Last edited by blackholeneo (2024-07-30 15:28:50)

loqs

Member

Registered: 2014-03-06

Posts: 18,467

Re: [solved] Compiling V8 from AUR - can't compile and exit terminal

Is anything recorded in the system journal from the freeze? Have you tried to reduce the number of parallel jobs in the PKGBUILD such as by changing https://aur.archlinux.org/cgit/aur.git/ … =v8-r#n107 to:

  ninja -j1 -C $OUTFLD

would make ninja run only one jobs at a time.

Last edited by loqs (2024-07-29 18:42:34)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,863

Website

Re: [solved] Compiling V8 from AUR - can't compile and exit terminal

Mod note: moving to AUR Issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

blackholeneo

Member

Registered: 2024-07-29

Posts: 3

Re: [solved] Compiling V8 from AUR - can't compile and exit terminal

Is anything recorded in the system journal from the freeze? Have you tried to reduce the number of parallel jobs in the PKGBUILD such as by changing https://aur.archlinux.org/cgit/aur.git/ … =v8-r#n107 to:

  ninja -j1 -C $OUTFLD

would make ninja run only one jobs at a time.

Thanks for the response. I didn't saw the system journal, and it looks like the system got out of memory (physical and swap):

jul 29 14:09:04 ArchVivoBook kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole@65d4f943fba44ea7b88cebb31b278dea.service,task=cc1plus,pid=23653,uid=1000
jul 29 14:09:04 ArchVivoBook kernel: Out of memory: Killed process 23653 (cc1plus) total-vm:2200940kB, anon-rss:431120kB, file-rss:556kB, shmem-rss:0kB, UID:1000 pgtables:4252kB oom_score_adj:200
jul 29 14:09:04 ArchVivoBook kernel: Purging GPU memory, 32 pages freed, 12698 pages still pinned, 0 pages left available.
jul 29 14:09:04 ArchVivoBook kernel: Purging GPU memory, 32 pages freed, 12666 pages still pinned, 0 pages left available.
jul 29 14:09:04 ArchVivoBook systemd[1]: user@1000.service: A process of this unit has been killed by the OOM killer.
jul 29 14:09:04 ArchVivoBook systemd[686]: app-org.kde.konsole@65d4f943fba44ea7b88cebb31b278dea.service: A process of this unit has been killed by the OOM killer.
jul 29 14:09:07 ArchVivoBook kernel: oom_reaper: reaped process 23653 (cc1plus), now anon-rss:292kB, file-rss:428kB, shmem-rss:0kB
jul 29 14:09:07 ArchVivoBook systemd[686]: app-org.kde.konsole@65d4f943fba44ea7b88cebb31b278dea.service: Failed with result 'oom-kill'.
jul 29 14:09:07 ArchVivoBook systemd[686]: app-org.kde.konsole@65d4f943fba44ea7b88cebb31b278dea.service: Consumed 12h 12min 26.086s CPU time, 6.6G memory peak, 7.1G memory swap peak.
jul 29 14:09:24 ArchVivoBook plasmashell[905]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
jul 29 14:09:24 ArchVivoBook plasmashell[905]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.

I will try to make ninja run only one job. Wish me luck.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,901

Re: [solved] Compiling V8 from AUR - can't compile and exit terminal

Ninja is notorious for being resource greedy, a few other mitigations you can also try :

- increase swap substantially (like to 24 GiB )
- make sure you're not building on tmpfs by setting TMPDIR to a folder on your ssd
- the graphic card doesn't seen to have dedicated memory, if that's correct reducing the resolution would also help
- Does the log show coredumps during compiling ? If so, disable them (temporarily) .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

blackholeneo

Member

Registered: 2024-07-29

Posts: 3

Re: [solved] Compiling V8 from AUR - can't compile and exit terminal

Thank you for the responses. Finally the problem was solved by making ninja work only one job at a time. The compilation process was longer than I tought but it finished without crashes. In the future I will try your recomendations, Lone_Wolf.