Arch Linux User Repository

I got the following error during the build() process. What can I do?

/src/calendar/date/CalendarInvites.ts
sanitizer-ebf9c13c.js  21.5908203125K
libs/purify.js
/src/misc/HtmlSanitizer.ts
native-common-c493486c.js  2.08203125K
/src/native/common/FileApp.ts
jszip-474a7d11.js  94.8271484375K
libs/jszip.js
polyfill-helpers-732b0afa.js  0.509765625K
commonjsHelpers.js

<--- Last few GCs --->

[11881:0x57b0810]   150218 ms: Mark-sweep (reduce) 2041.2 (2083.8) -> 2039.2 (2083.8) MB, 888.0 / 0.0 ms  (average mu = 0.166, current mu = 0.150) allocation failure scavenge might not succeed
[11881:0x57b0810]   151180 ms: Mark-sweep (reduce) 2040.6 (2083.8) -> 2039.3 (2083.8) MB, 950.3 / 0.0 ms  (average mu = 0.093, current mu = 0.013) allocation failure scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb09980 node::Abort() [node]
 2: 0xa1c235 node::FatalError(char const*, char const*) [node]
 3: 0xcf784e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xcf7bc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xeaf465  [node]
 6: 0xeaff46  [node]
 7: 0xebe46e  [node]
 8: 0xebeeb0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xec1e2e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xe8336a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11: 0x11fc0b6 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x15f0b19  [node]
/home/uSER/AUR/tutanota-desktop/PKGBUILD: line 37: 11881 Aborted                 (core dumped) node desktop --custom-desktop-release --unpacked
==> ERROR: A failure occurred in build().
    Aborting...

Could we swap nvm for nodenv ?

@evilrobot: I'd prefer to wait until upstream adds official support.

I was able to get an arm64 build of 3.91.2 based on https://github.com/tutao/tutanota/blob/master/doc/BUILDING.md#building-and-running-your-own-tutanota-desktop-client and a few changes to buildSrc/electron-package-json-template.js (based on https://github.com/tutao/tutanota/pull/3020).

Would you possibly consider updating the package to build from release source, so that we can have aarch64 support please? Havent created a package yet but could give it a go if you think this is better as a separate package.

diff --git a/buildSrc/electron-package-json-template.js b/buildSrc/electron-package-json-template.js
index 8d57ead03..a1f547340 100644
--- a/buildSrc/electron-package-json-template.js
+++ b/buildSrc/electron-package-json-template.js
@@ -81,7 +81,7 @@ export default function generateTemplate({nameSuffix, version, updateUrl, iconPa
                        "productName": nameSuffix.length > 0
                                ? nameSuffix.slice(1) + " Tutanota Desktop"
                                : "Tutanota Desktop",
-                       "artifactName": "${name}-${os}.${ext}",
+                       "artifactName": "${name}-${os}-${arch}.${ext}",
                        "afterSign": notarize ? "buildSrc/notarize.cjs" : undefined,
                        "protocols": [
                                {
@@ -125,7 +125,7 @@ export default function generateTemplate({nameSuffix, version, updateUrl, iconPa
                                "target": [
                                        {
                                                "target": unpacked ? "dir" : "nsis",
-                                               "arch": "x64"
+                                               "arch": ["x64", "arm64"]
                                        }
                                ]
                        },
@@ -171,7 +171,7 @@ export default function generateTemplate({nameSuffix, version, updateUrl, iconPa
                                "target": [
                                        {
                                                "target": unpacked ? "dir" : "AppImage",
-                                               "arch": "x64"
+                                               "arch": ["x64", "arm64"]
                                        }
                                ]
                        }

increase the memory for node (default is 4096):

export NODE_OPTIONS=--max_old_space_size=8192

set the NODE_OPTIONS env in the shell / or PKGBUILD, before you build the package.

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 1: 0x560179bd26b1 node::Abort() [node] 2: 0x560179ad8ceb node::FatalError(char const, char const) [node] 3: 0x560179db2782 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [node] 4: 0x560179db29e8 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [node] 5: 0x560179f582c6 [node] 6: 0x560179f69bf2 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node] 7: 0x560179f6beca v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 8: 0x560179f6bf57 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 9: 0x560179f2fa5d v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node] 10: 0x56017a280429 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long, v8::internal::Isolate) [node] 11: 0x56017a633bf9 [node] [redacted]/.cache/yay/tutanota-desktop/PKGBUILD: line 20: 21936 Aborted (core dumped) node dist -l --custom-desktop-release --unpacked

Getting this build error trying to update 3.91.2-1 from the one below it, anyone know why?

I get this error for a few weeks now. Still stuck with version 3.84.7-1: Build error: ExecError: npm exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE Error output: npm ERR! code ETARGET npm ERR! notarget No matching version found for electron-updater@4.3.5. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.

Build error: ExecError: npm exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE Error output: npm ERR! code ETARGET npm ERR! notarget No matching version found for fs-extra@^9.0.1. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.

@IEPforAUR: I can't reproduce that.

"Build error: ExecError: npm exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE"