Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

koii-node 0.5.0 crashed with javascript heap size error #8

Open
flogat opened this issue Feb 19, 2024 · 0 comments
Open

koii-node 0.5.0 crashed with javascript heap size error #8

flogat opened this issue Feb 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@flogat
Copy link

flogat commented Feb 19, 2024

🐛 What issue do you have?

After about a day or so of running, the node crashed.

OS Details

koii2@koii2:~$ uname -a
Linux koii2 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

I observed this in the log, all timestamps in CET+1.

8:21:31.535 › (node:535977) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
18:21:31.539 › Error in handleEvents Error: 502 Bad Gateway: <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]>    <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>

<title>testnet.koii.live | 502: Bad gateway</title>

Then several hundred times the following rows:

18:21:31.551 › null delay
18:21:31.551 › (node:535977) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.
Timeout duration was set to 1.

And eventually

18:21:41.623 › (node:535977) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
18:21:41.625 › null delay
18:21:41.626 › (node:535977) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
18:21:41.626 › null delay
18:21:41.627 › (node:535977) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.
Timeout duration was set to 1.

<--- Last few GCs --->

[535977:0x1ef000390000] 35985014 ms: Scavenge 1898.4 (2063.0) -> 1893.3 (2063.2) MB, 5.46 / 0.02 ms  (average mu = 0.306, current mu = 0.200) task;
[535977:0x1ef000390000] 35985243 ms: Scavenge 1898.9 (2063.2) -> 1893.8 (2063.7) MB, 8.72 / 0.02 ms  (average mu = 0.306, current mu = 0.200) task;
[535977:0x1ef000390000] 35985519 ms: Scavenge 1899.6 (2063.7) -> 1894.5 (2064.5) MB, 8.16 / 0.02 ms  (average mu = 0.306, current mu = 0.200) task;


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Let me know shoud you need any further details.

🌐 Desktop Node Version

0.5.0

🖥️ Operating System

Ubuntu

🔑 System Key

12Fx6CYaJEisy4oWZGxwukGmwweR4q8eNZzrCKzGSH1M

Task ID

No response

Steps to reproduce

I was running these 4 tasks:
image
@flogat flogat added the bug Something isn't working label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@flogat