Replies: 1 comment
-
nobody case me.... I have solved it. so it can close. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
nobody case me.... I have solved it. so it can close. |
Beta Was this translation helpful? Give feedback.
-
I'm just study extension development. first ,i can build well. but when I edited the code . I just comment the code like this
}else if (!DEBUG && !TEST) {
/*
chrome.runtime.onInstalled.addListener(({reason}) => {
if (reason === 'install') {
chrome.tabs.create({url: getHelpURL()});//getHelpURL()
}
});
*/
chrome.runtime.setUninstallURL(UNINSTALL_URL);
}
then npm run build got the error here:
<--- Last few GCs --->
[35816:000002A09C1AFA40] 41838 ms: Mark-Compact 3036.7 (3110.0) -> 3025.8 (3114.2) MB, 1313.51 / 0.00 ms (average mu = 0.430, current mu = 0.029) allocation failure; scavenge might not succeed
[35816:000002A09C1AFA40] 44521 ms: Mark-Compact 3042.1 (3114.7) -> 3031.9 (3120.2) MB, 2647.35 / 0.00 ms (average mu = 0.180, current mu = 0.013) allocation failure; scavenge might not succeed
[35816:000002A09C1AFA40] 44521 ms: Mark-Compact 3042.1 (3114.7) -> 3031.9 (3120.2) MB, 2647.35 / 0.00 ms (average mu = 0.180, current mu = 0.013) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 00007FF60BD571AB node::SetCppgcReference+16075
2: 00007FF60BCCDCC6 v8::base::CPU::num_virtual_address_bits+79190
Beta Was this translation helpful? Give feedback.
All reactions