I created Native Messaging hosts in several programming languages including
C, C++, JavaScript. In JavaScript I created a host specific to QuickJS,
Node.js, Deno. Node.js and Deno depend on V8. I use the same call in the
extension to create hosts
globalThis.name = chrome.runtime.getManifest().short_name;
globalThis.port = chrome.runtime.connectNative(globalThis.name);
port.onMessage.addListener((message) => console.log(message));
port.onDisconnect.addListener((p) => console.log(chrome.runtime.lastError));
port.postMessage(new Array(200000));
chrome.runtime.onInstalled.addListener((reason) => {
console.log(reason);
});
The same code used to work on Chromium Dev Channel. Now the V8 JavaScript
engine-specific versions increase memory usage exponentially to upwards of
1GB, then exit.
The input is echoed when the input array is 2000.
Appears to be some kind of caching or process blocking. I am not sure
though.
Any recent changes that impact buffering or caching procceses?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/v8-users/abda324f-a27b-4f35-901e-28b5b9a7753fn%40googlegroups.com.
