René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"node_http_parser.cc:1096:static void node::{anonymous}::ConnectionsList::Expired with NodeJS v18.17.0","articleBody":"### Version\n\n18.17.0\n\n### Platform\n\nLinux xxxxxx 4.18.0-477.15.1.el8_8.x86_64 #1 SMP Fri Jun 2 08:27:19 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nUpgraded the Node JS to v18.17.0, created docker image for node application.\r\nDeployed the image, server getting stared and DB connection established. \r\nafter 2-3 seconds, below error thrown and pod goes to CrashLoopBackOff status continously./\r\n\r\nError:\r\nnode[1]: ../src/node_http_parser.cc:1096:static void node::{anonymous}::ConnectionsList::Expired(const v8::FunctionCallbackInfo\u003cv8::Value>&): Assertion `args[0]->IsNumber()' failed.\r\n 1: 0xb83f50 node::Abort() [node]\r\n 2: 0xb83fce  [node]\r\n 3: 0xba415a  [node]\r\n 4: 0xdc28b0  [node]\r\n 5: 0xdc3def v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]\r\n 6: 0x17036b9  [node]\n\n### How often does it reproduce? Is there a required condition?\n\n_No response_\n\n### What is the expected behavior? Why is that the expected behavior?\n\nNode application pod should be running without any crashing.\n\n### What do you see instead?\n\nBelow error:\r\nError:\r\nnode[1]: ../src/node_http_parser.cc:1096:static void node::{anonymous}::ConnectionsList::Expired(const v8::FunctionCallbackInfo\u003cv8::Value>&): Assertion `args[0]->IsNumber()' failed.\r\n 1: 0xb83f50 node::Abort() [node]\r\n 2: 0xb83fce  [node]\r\n 3: 0xba415a  [node]\r\n 4: 0xdc28b0  [node]\r\n 5: 0xdc3def v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]\r\n 6: 0x17036b9  [node]\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/Ganeshfair","@type":"Person","name":"Ganeshfair"},"datePublished":"2023-08-25T10:55:34Z","url":"https://github.com/nodejs/node/issues/49324"}