[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294620] www/onlyoffice-documentserver: pkg builds fail on aarch64"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 18 Apr 2026 18:44:19 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294620
Bug ID: 294620
Summary: www/onlyoffice-documentserver: pkg builds fail on
aarch64
Product: Ports & Packages
Version: Latest
Hardware: arm64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: fsbruva@yahoo.com
Several successive pkg-fallout entries on aarch64 indicate a real build issue,
caused by node out of memory error.
Error occurs during babel is likely caused by upgraded node version (to
20.20.2, via npm-node20 dependency). Error message:
<--- Last few GCs --->
[44204:0x126adf4fde40] 80056 ms: Scavenge 502.0 (516.1) -> 501.5 (516.9) MB,
5.96 / 0.00 ms (average mu = 0.477, current mu = 0.310) allocation failure;
[44204:0x126adf4fde40] 80071 ms: Scavenge 502.8 (516.9) -> 502.4 (521.6) MB,
9.04 / 0.00 ms (average mu = 0.477, current mu = 0.310) allocation failure;
[44204:0x126adf4fde40] 81315 ms: Mark-Compact 505.5 (521.6) -> 504.2 (524.4)
MB, 1231.29 / 0.00 ms (average mu = 0.274, current mu = 0.039) allocation
failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of
memory
----- Native stack trace -----
1: 0x177b000 node::OOMErrorHandler(char const*, v8::OOMDetails const&)
[/usr/local/bin/node]
2: 0x1958398 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*,
char const*, v8::OOMDetails const&) [/usr/local/bin/node]
3: 0x1b3ec4c
v8::internal::Heap::GarbageCollectionReasonToString(v8::internal::GarbageCollectionReason)
[/usr/local/bin/node]
4: 0x1b3d898 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace,
v8::internal::GarbageCollectionReason, v8::GCCallbackFlags)
[/usr/local/bin/node]
5: 0x1b345d4
v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int,
v8::internal::AllocationType, v8::internal::AllocationOrigin,
v8::internal::AllocationAlignment) [/usr/local/bin/node]
6: 0x1b34b94
v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int,
v8::internal::AllocationType, v8::internal::AllocationOrigin,
v8::internal::AllocationAlignment) [/usr/local/bin/node]
7: 0x1b1a924 v8::internal::Factory::NewFillerObject(int,
v8::internal::AllocationAlignment, v8::internal::AllocationType,
v8::internal::AllocationOrigin) [/usr/local/bin/node]
gn gen out.gn/freebsd_64 --args="v8_monolithic=true is_debug=false
v8_static_library=true is_component_build=false is_clang=true use_sysroot=false
treat_warnings_as_errors=false clang_use_chrome_plugins=false use_lld=true
use_custom_libcxx=false v8_use_external_startup_data=false
is_component_build=false"
Patch forthcoming.
--
You are receiving this mail because:
You are the assignee for the bug.