node.js - wasm 代码提交分配失败

node.js - wasm 代码提交分配失败 - 进程内存不足

转载作者：行者123 更新时间：2023-12-03 12:11:07

我有一个 nodejs 脚本，它在 nodejs 12 上运行良好。我有一个新的 macbook air，我在上面安装了 nodejs LTS 14。脚本没有按预期工作，所以我将它降级到 nodejs 12 LTS。现在我收到进程内存不足的错误。我也尝试使用 --max-oud-size 来增加内存分配。 export NODE_OPTIONS=--max_old_space_size=4096它没有用。以下是错误的堆栈跟踪


<--- Last few GCs --->

[8193:0x150008000]       41 ms: Scavenge 2.9 (4.9) -> 2.7 (5.7) MB, 0.5 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
[8193:0x150008000]       54 ms: Scavenge 3.9 (5.9) -> 3.6 (8.6) MB, 0.3 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
[8193:0x150008000]       59 ms: Scavenge 5.2 (8.6) -> 3.9 (9.1) MB, 0.2 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 


<--- JS stacktrace --->

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

Security context: 0x00010b1808d1 <JSObject>
    0: builtin exit frame: new constructor(aka Module)(this=0x000102ea1961 <Object map = 0x10b3ecbc9>,0x000102ea1811 <Uint8Array map = 0x102fc2b99>,0x000102ea1961 <Object map = 0x10b3ecbc9>)

    1: ConstructFrame [pc: 0x100ca8758]
    2: StubFrame [pc: 0x100d91204]
    3: /* anonymous */ [0x102ea10b1] [/Applications/XAMPP/xamppfiles/htdocs/web-dev/local-cron-jobs/node_modules/long/src/long.js:9...

FATAL ERROR: wasm code commit Allocation failed - process out of memory
 1: 0x1004db324 node::Abort() [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 2: 0x1004db4a4 node::errors::TryCatchScope::~TryCatchScope() [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 3: 0x1005fab78 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 4: 0x1005fab0c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 5: 0x100b332bc v8::internal::wasm::WasmCodeAllocator::AllocateForCodeInRegion(v8::internal::wasm::NativeModule*, unsigned long, v8::base::AddressRegion) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 6: 0x100b34198 v8::internal::wasm::NativeModule::CreateEmptyJumpTableInRegion(unsigned int, v8::base::AddressRegion) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 7: 0x100b33660 v8::internal::wasm::NativeModule::AddCodeSpace(v8::base::AddressRegion) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 8: 0x100b33fd4 v8::internal::wasm::NativeModule::NativeModule(v8::internal::wasm::WasmEngine*, v8::internal::wasm::WasmFeatures const&, bool, v8::internal::VirtualMemory, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>, std::__1::shared_ptr<v8::internal::Counters>, std::__1::shared_ptr<v8::internal::wasm::NativeModule>*) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
 9: 0x100b36214 v8::internal::wasm::WasmCodeManager::NewNativeModule(v8::internal::wasm::WasmEngine*, v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, unsigned long, bool, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
10: 0x100b3cb1c v8::internal::wasm::WasmEngine::NewNativeModule(v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, unsigned long, bool, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
11: 0x100b3ca64 v8::internal::wasm::WasmEngine::NewNativeModule(v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
12: 0x100b14578 v8::internal::wasm::CompileToNativeModule(v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, v8::internal::wasm::ErrorThrower*, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>, v8::internal::wasm::ModuleWireBytes const&, v8::internal::Handle<v8::internal::FixedArray>*) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
13: 0x100b3a710 v8::internal::wasm::WasmEngine::SyncCompile(v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, v8::internal::wasm::ErrorThrower*, v8::internal::wasm::ModuleWireBytes const&) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
14: 0x100b5bc98 v8::(anonymous namespace)::WebAssemblyModule(v8::FunctionCallbackInfo<v8::Value> const&) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
15: 0x10065f150 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
16: 0x10065e4b8 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<true>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
17: 0x10065dfb4 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
18: 0x100d2b0cc Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
19: 0x100ca8758 Builtins_JSBuiltinsConstructStub [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
20: 0x100d91204 Builtins_ConstructHandler [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
21: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
22: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
23: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
24: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
25: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
26: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
27: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
28: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
29: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
30: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
31: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
32: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
33: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
34: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
35: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
36: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
37: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
38: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
39: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
40: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
41: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
42: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
43: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
44: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
45: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
46: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
47: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
48: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
49: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
50: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
51: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
52: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
53: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
54: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
55: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
56: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
57: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
58: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
59: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
60: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
61: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
62: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
63: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
64: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
65: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
66: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
67: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
68: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
69: 0x100cad520 Builtins_InterpreterEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
70: 0x100caa5a8 Builtins_JSEntryTrampoline [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
71: 0x100caa24c Builtins_JSEntry [/Users/rahulbharati/.nvm/versions/node/v12.20.1/bin/node]
72: 0x150008000 ```

Any help appreciated. Thanks.

最佳答案

此问题已在 Node 15.3.0 中得到修复.
我更新了我的，对我来说效果很好。

关于node.js - wasm 代码提交分配失败 - 进程内存不足，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/65856300/

文章推荐： R生成一个1分钟的间隔时间序列

文章推荐： r - 从一个区间生成一组随机的唯一整数

文章推荐： node.js - brew 错误 : No available formula with the name "node@11"

c - WASM : does anyone support multi-value WASM?
将多个值从 WebAssembly 传递到 Javascript 可能比需要的更难。通常，我发现我必须: 设置 Javascript 和 WebAssembly 之间共享的内存。执行 WASM 工作
Flutter:wasm 流编译失败:TypeError:无法下载 wasm 模块
我正在构建一个 Flutter 网络应用程序。一切正常，直到随机进行了热重启，然后我开始收到此错误。 wasm streaming compile failed: TypeError: Could n
rust - 如何在不使用 wasm-pack 的情况下将 Rust 项目编译为 Wasm？
我想使用 python-ext-wasm 将 Rust 程序/项目编译为 Wasm，以便在我的 Python 应用程序中使用.现有的教程假定它是针对网络的并建议 wasm-pack .有没有另一种在没
typescript - 如何在 typescript 文件中导入由 wasm-pack 生成的 wasm 文件？
脚步:cargo generate --git https://github.com/rustwasm/wasm-pack-template项目名称:project-name // src/lib.r
rust - 生成返回字符串的函数时，为什么 wasm-opt 在 wasm-pack 构建中失败？
我正在处理 Rust WASM tutorial for Conway's game of life . 文件中最简单的函数之一叫做 Universe.render (它用于呈现代表游戏状态的字符串)
rust - 如何在以 WASM 为目标的 near-sdk Rust 代码中链接 WASM 二进制文件
我有一个 WASM 函数，我想在我的以 WASM 为目标的 near-sdk Rust 项目中使用。我如何在我的 Rust 代码中调用这个函数？最佳答案您的情况还不够详细，无法给出详细的答案。 (
javascript - 使用 Emscripten 将 C++ 代码编译为独立的 Wasm 会导致 .wasm 需要某些导入函数
我正在尝试使用 Emscripten 作为学习机会将完整的 C++ 程序编译为 Wasm。以下命令确实生成了完整有效且有效的 HTML+JS+Wasm: emcc main.cpp [...libra
rust - 如何通过 wasm-pack 将 Rust Wasm 应用程序与 libpq 链接起来？
我正在尝试创建一个带有 Wasm 数据库层的 NodeJS 应用程序。我使用 Rust、Diesel 作为数据库驱动程序，使用 wasm-pack 作为 WebAssembly 编译器。当我尝试使用
rust - 为什么在 Rust/Wasm 初学者书籍的第 4.2 节中，从 JavaScript 传递到 Wasm 的字符串总是空的？
我正在尝试关注 Rust WebAssembly book我被困在第 4.2 节的练习中。我按照答案中的描述更改了所有内容，但是给定的 &str (姓名)在greet函数始终为空。这是我的 gree
angular - 在使用 SourceMapConsumer 之前，您必须通过调用 SourceMapConsumer.initialize({ 'lib/mappings.wasm' : . .. }) 提供 lib/mappings.wasm 的 URL
我在构建项目(Angular 8)时遇到上述错误。我们如何修复这个错误？最佳答案 $env:NODE_OPTIONS = "--no-experimental-fetch" 在 Power shel
docx-wasm - wasm中的br_if怎么理解？
br_if 是如何工作的。我已经阅读了文档，但我没有找到任何关于 br_if 的结果值的信息。我用 WebAssembly Studio .我有这段代码，但我不明白为什么会这样。 (func $f (
Go WASM 导出功能
我想创建一个 .wasm编译时仍具有导出的函数名称的文件。 package main import ( "fmt" ) func main() { fmt.Println("Main"
Blazor WASM 没有达到断点
我有一个带有版本 5 程序集的 Blazor WASM 项目，并尝试根据这篇文章激活调试:https://docs.microsoft.com/en-us/aspnet/core/blazor/deb
Blazor wasm 中的多线程
我正在使用 Blazor WASM 开发简单的在线游戏。最近我发现 Blazor 客户端是单线程的，这对于我的大多数算法来说都是灾难性的。我想实现比权威服务器更好的架构，并能够在客户端运行代码(用于滞
c# - 在客户端 wasm 代码中包含密码是否安全？
由于 Wasm 是以非人类可读的形式编写的，这是否使黑客几乎不可能查看站点的 Wasm 文件并弄清楚是什么？我知道在客户端保留敏感数据从来都不是最佳实践，但在代码模糊性方面，Wasm 似乎有点改变游
webassembly - 如何在 wasm 中生成导入部分？
当我们将一个c源文件编译成wasm时，会有很多import "env"xxxx段。比如这是我的c源文件， char message[] = "hello wasm!"; char* getMessag
c++ - 如何减小 WASM 二进制文件的大小？
我有一个用 C++ 编写的项目，要部署的平台的二进制大小限制为 256KB。工具链是wasi-sdk-16.0 clang++，我们使用这个编译器将源代码编译成WASM格式的二进制文件。在此步骤中，
c# - Blazor wasm 本地化仅显示键
已关注 Dynamically set the culture from the Accept-Language header本地化我的 blazor wasm 应用程序。 WebUI.csproj
c# - 无法调试 Blazor wasm
我正在使用 vscode。我无法调试“独立”(或“托管”)blazor wasm。有很多这样的问题，但它们是针对 RC、显然已为 .NET 6 修复的错误，或显然已在 SDK 6.0.102 中修复
rust - 如何优化原生和 WASM 工具链的可执行二进制文件的大小？
我是 Rust 的新手，到目前为止我对它的设计感到惊讶。但是我遇到了一些让我害怕在商业项目中使用它的事情。 “Hello world”应用程序的可执行二进制文件大小为 3.2Mb。 -rwxr-xr-

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

node.js - wasm 代码提交分配失败 - 进程内存不足