Node 22.5.0 started to crash and hangs on different cases #53902

zloirock · 2024-07-17T18:20:56Z

Version

22.5.0

Platform

macOS 15.0, M1

What steps will reproduce the bug?

Now I haven't much time to properly debug it, so a couple of cases:

Clone core-js repo.

npm i just hangs on.

Ok, if we somehow install dependencies and run npm test, Node crashes with:

FATAL ERROR: v8::Object::GetCreationContextChecked No creation context available
----- Native stack trace -----

 1: 0x104a4e230 node::OnFatalError(char const*, char const*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 2: 0x104c20898 v8::Utils::ReportApiFailure(char const*, char const*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 3: 0x104c358fc v8::Object::GetCreationContextChecked() [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 4: 0x104a55f88 node::fs::FastClose(v8::Local<v8::Object>, int, v8::FastApiCallbackOptions&) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 5: 0x10b9accc4 
 6: 0x1056a6c0c Builtins_JSEntryTrampoline [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 7: 0x1056a68f4 Builtins_JSEntry [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 8: 0x104d50564 v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 9: 0x104d4fadc v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
10: 0x104c369cc v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
11: 0x104970fa0 node::InternalMakeCallback(node::Environment*, v8::Local<v8::Object>, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
12: 0x104987d8c node::AsyncWrap::MakeCallback(v8::Local<v8::Function>, int, v8::Local<v8::Value>*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
13: 0x104a53ca4 node::fs::FSReqCallback::Resolve(v8::Local<v8::Value>) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
14: 0x104a549a8 node::fs::AfterInteger(uv_fs_s*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
15: 0x104a482fc node::MakeLibuvRequestCallback<uv_fs_s, void (*)(uv_fs_s*)>::Wrapper(uv_fs_s*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
16: 0x105684a70 uv__work_done [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
17: 0x105688544 uv__async_io [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
18: 0x10569ab08 uv__io_poll [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
19: 0x105688b08 uv_run [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
20: 0x104971714 node::SpinEventLoopInternal(node::Environment*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
21: 0x104a8f8f0 node::NodeMainInstance::Run(node::ExitCode*, node::Environment*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
22: 0x104a8f688 node::NodeMainInstance::Run() [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
23: 0x104a15928 node::Start(int, char**) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
24: 0x18b2cf274 start [/usr/lib/dyld]


#
# Fatal error in , line 0
# Missing deoptimization information for OptimizedFrame::Summarize.
#
#
#
#FailureMessage Object: 0x16b488648
----- Native stack trace -----

 1: 0x104ab7a4c node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 2: 0x105f3e5d4 V8_Fatal(char const*, ...) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 3: 0x104d5993c v8::internal::OptimizedFrame::Summarize(std::__1::vector<v8::internal::FrameSummary, std::__1::allocator<v8::internal::FrameSummary>>*) const [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 4: 0x104d62c60 v8::internal::Isolate::CaptureDetailedStackTrace(int, v8::StackTrace::StackTraceOptions) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 5: 0x104c2ace0 v8::StackTrace::CurrentStackTrace(v8::Isolate*, int, v8::StackTrace::StackTraceOptions) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 6: 0x104a4cc0c node::GetCurrentStackTrace(v8::Isolate*, int) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 7: 0x1049b869c node::DumpJavaScriptBacktrace(__sFILE*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 8: 0x104a4e238 node::OnFatalError(char const*, char const*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
 9: 0x104c20898 v8::Utils::ReportApiFailure(char const*, char const*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
10: 0x104c358fc v8::Object::GetCreationContextChecked() [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
11: 0x104a55f88 node::fs::FastClose(v8::Local<v8::Object>, int, v8::FastApiCallbackOptions&) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
12: 0x10b9accc4 
13: 0x1056a6c0c Builtins_JSEntryTrampoline [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
14: 0x1056a68f4 Builtins_JSEntry [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
15: 0x104d50564 v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
16: 0x104d4fadc v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
17: 0x104c369cc v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
18: 0x104970fa0 node::InternalMakeCallback(node::Environment*, v8::Local<v8::Object>, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
19: 0x104987d8c node::AsyncWrap::MakeCallback(v8::Local<v8::Function>, int, v8::Local<v8::Value>*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
20: 0x104a53ca4 node::fs::FSReqCallback::Resolve(v8::Local<v8::Value>) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
21: 0x104a549a8 node::fs::AfterInteger(uv_fs_s*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
22: 0x104a482fc node::MakeLibuvRequestCallback<uv_fs_s, void (*)(uv_fs_s*)>::Wrapper(uv_fs_s*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
23: 0x105684a70 uv__work_done [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
24: 0x105688544 uv__async_io [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
25: 0x10569ab08 uv__io_poll [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
26: 0x105688b08 uv_run [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
27: 0x104971714 node::SpinEventLoopInternal(node::Environment*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
28: 0x104a8f8f0 node::NodeMainInstance::Run(node::ExitCode*, node::Environment*) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
29: 0x104a8f688 node::NodeMainInstance::Run() [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
30: 0x104a15928 node::Start(int, char**) [/Users/denispuskarev/.nvm/versions/node/v22.5.0/bin/node]
31: 0x18b2cf274 start [/usr/lib/dyld]
/bin/bash: line 1: 92352 Trace/BPT trap: 5       npm run build-compat

on this script.

The same error happens, for example, if we somehow built it (for example, with the previous Node version) and run other scripts like this.

In most of those cases used zx and / or konan.

Sure, before Node 22.5.0, everything worked fine.

The text was updated successfully, but these errors were encountered:

RedYetiDev · 2024-07-17T18:29:53Z

Given the stack trace you've produced, I've optimistically applied the fs and v8 engine labels, but those can always be changed.

cjihrig · 2024-07-17T18:31:20Z

#53627 seems like the likely culprit.

RedYetiDev · 2024-07-17T18:33:32Z

Also, for reference, the erroring line is

node/src/node_file.cc

Line 994 in 7b573d1

Environment* env = Environment::GetCurrent(recv->GetCreationContextChecked());

merceyz · 2024-07-17T18:42:50Z

Similar issue showing up in Yarn (yarnpkg/berry#6398), it either hangs or if run with CI=true then node stops mid execution without an error code.
Bisects to #53627.

RedYetiDev · 2024-07-17T18:49:52Z

I've opened a revert PR #53904 if this needs to be reverted.

anonrig · 2024-07-17T19:32:24Z

@joyeecheung Any idea how is this possible?

v8::Object::GetCreationContextChecked No creation context available

anonrig · 2024-07-17T19:48:10Z

This needs a better repro than the following command which runs 10+ subprocesses.

npm run r (that's cleaning + installing dependencies + npm test) just hangs on.

RedYetiDev · 2024-07-17T19:49:28Z

https://github.com/latin-1/berry-node-22.5.0-broken/ is slightly better, but not perfect.

STREAM 55954: do read
STREAM 55954: push null
STREAM 55954: onEofChunk
STREAM 55954: emitReadable_
STREAM 55954: flow
STREAM 55954: read undefined
STREAM 55954: endReadable
STREAM 55954: endReadableNT
Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)

anonrig · 2024-07-17T20:01:19Z

I can not test it locally, but technically this should fix the bug: #53910

targos · 2024-07-17T20:01:23Z

I think we should hold on landing future fast API pull requests until we have a way to guarantee that the added code paths are tested.

anonrig · 2024-07-17T20:09:58Z

OK I found a reproduction, and the fix I proposed works.

Here's the repro:

const fs = require('fs')

let failed;
for (let i = 0; i < 1_000_000; i++) {
  failed = fs.readFile('./configure.py', (err, done) => {
    // do nothing
    console.log(err, done)
  })
}
console.log(failed)

I think we should hold on landing future fast API pull requests until we have a way to guarantee that the added code paths are tested.

Agreed.

merceyz · 2024-07-17T20:21:18Z

https://github.com/latin-1/berry-node-22.5.0-broken/ is slightly better, but not perfect.

@RedYetiDev Note that the issue happens in the yarn step where the process exits early without an error, yarn build fails because yarn failed.

merceyz · 2024-07-17T20:44:08Z

I can not test it locally, but technically this should fix the bug: #53910

#53910 doesn't fix #53902 (comment) but reverting #53627 does.

RedYetiDev · 2024-07-17T22:05:46Z

I can not test it locally, but technically this should fix the bug: #53910

#53910 doesn't fix #53902 (comment) but reverting #53627 does.

#53904?

anonrig · 2024-07-17T22:21:29Z

#53910 doesn't fix #53902 (comment) but reverting #53627 does.

#53910 fixes the issue. What makes you think that it doesn't fix the issue?

latin-1 · 2024-07-17T22:51:46Z

@anonrig They might be two different issues with FastClose, I guess? The yarn one does not crash; it hangs/exits without leaving any stack traces.

anonrig · 2024-07-17T23:04:57Z

@anonrig They might be two different issues with FastClose, I guess? The yarn one does not crash; it hangs/exits without leaving any stack traces.

If that's the issue, can you open a different/new issue with a reproducible test case?

merceyz · 2024-07-17T23:07:31Z

#53910 doesn't fix #53902 (comment) but reverting #53627 does.

#53910 fixes the issue. What makes you think that it doesn't fix the issue?

Not the one I linked to in that comment.

I can not test it locally, but technically this should fix the bug: #53910

#53910 doesn't fix #53902 (comment) but reverting #53627 does.

#53904?

Yeah, with that PR (or when I git revert #53627 on v22.5.0) the yarn command completes successfully.

nicomsz · 2024-07-19T21:42:03Z

The https://github.com/nodejs/node/releases/tag/v22.5.1 was just published. Please upgrade back to v22.5.1 or 22.x or latest, if you're pinned your version to v22.4.1

how can i upgrade to v22.5.1 on docker? it is returning me that error: ERROR: failed to solve: node:22.5.1: failed to resolve source metadata for docker.io/library/node:22.5.1: no match for platform in manifest: not found

melroy89 · 2024-07-19T22:03:49Z

The https://github.com/nodejs/node/releases/tag/v22.5.1 was just published. Please upgrade back to v22.5.1 or 22.x or latest, if you're pinned your version to v22.4.1

how can i upgrade to v22.5.1 on docker? it is returning me that error: ERROR: failed to solve: node:22.5.1: failed to resolve source metadata for docker.io/library/node:22.5.1: no match for platform in manifest: not found

Yup same..

trivikr · 2024-07-19T23:12:28Z

Node.js v22.5.1 is available on Docker since Jul 19, 2024 at 2:42 PM Pacific

https://hub.docker.com/layers/library/node/22.5.1/images/sha256-a18c05b559a62b7530390cbf9720e737fe04178530b8f5c49dbaac8f1c5f3a89?context=explore

It takes some time, as it's done using a PR by automation bot post-release which needs to be manually reviewed and merged.
Example automated PR for v22.5.1 nodejs/docker-node#2122

Fixes nodejs/node#53902

The CI builds started failing on node `v22.5.0` likely due to nodejs/node#53902 The NodeJS version on CI was therefore pinned to 21 in #272 This pull request goes back to using the latest NodeJS version, and should be merged to master once the issue with NodeJS `v22.5.0` noted above is fixed, and the build on this pull request succeeds.

This PR reverts #64, since nodejs/node#53902 has been resolved in [Node.js 22.5.1](https://nodejs.org/en/blog/release/v22.5.1).

…a patch.…" This reverts commit d2832db.

…a patch.…" (#2325) This reverts commit d2832db as node v22.5 is now patched

Reverts #16709 The underlying issue has been fixed in node 20.5.1 nodejs/node#53902 Fixes #16707

RedYetiDev added fs Issues and PRs related to the fs subsystem / file system. v8 engine Issues and PRs related to the V8 dependency. labels Jul 17, 2024

merceyz mentioned this issue Jul 17, 2024

[Bug?]: nodeLinker: node-modules is broken in Node.js 22.5.0 yarnpkg/berry#6398

Closed

1 task

RedYetiDev added confirmed-bug Issues with confirmed bugs. regression Issues related to regressions. v22.x v22.x Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch. labels Jul 17, 2024

RedYetiDev mentioned this issue Jul 17, 2024

Revert "fs: add v8 fast api to closeSync" #53904

Merged

cmwylie19 mentioned this issue Jul 17, 2024

feat: sanitizing store keys - store path v2 defenseunicorns/pepr#918

Merged

5 tasks

anonrig mentioned this issue Jul 17, 2024

fs: fix not found close creation context #53910

Closed

cmwylie19 mentioned this issue Jul 17, 2024

chore: node ci patch defenseunicorns/pepr#968

Closed

5 tasks

This comment has been minimized.

Sign in to view

rochdev mentioned this issue Jul 17, 2024

hardcode the latest version of node as 22.4 DataDog/dd-trace-js#4526

Merged

melroy89 mentioned this issue Jul 19, 2024

Revert "Bump to newer version that also fixes npm install (#930)" MbinOrg/mbin#931

Merged

This was referenced Jul 20, 2024

test: update test262 parser test meriyah/meriyah#279

Merged

Pin Node.js v22 version prettier/prettier#16491

Merged

Omochice mentioned this issue Jul 20, 2024

chore(deps): update dependency vitest to v2 Omochice/renovate-config#115

Merged

1 task

ryanking13 mentioned this issue Jul 20, 2024

Pin Node.js version in conda env and fix mypy tests pyodide/pyodide#4955

Merged

julienp mentioned this issue Jul 21, 2024

Revert "Pin node to 22.4.x to workaround breakage" pulumi/pulumi#16731

Merged

wellwelwel mentioned this issue Jul 22, 2024

ci: temp disable Node.js 22.x from matrix sidorares/node-mysql2#2870

Merged

pi-alexander-popel added a commit to postindustria-tech/location-node that referenced this issue Jul 22, 2024

options: pin newer Node version

f544c5c

Fixes nodejs/node#53902

pi-alexander-popel added a commit to postindustria-tech/pipeline-node that referenced this issue Jul 22, 2024

options: pin newer Node version

604c5ab

Fixes nodejs/node#53902

pi-alexander-popel added a commit to postindustria-tech/device-detection-node that referenced this issue Jul 22, 2024

options: pin newer Node version

aa494b5

Fixes nodejs/node#53902

pi-alexander-popel mentioned this issue Jul 22, 2024

options: pin newer Node version 51Degrees/pipeline-node#129

Merged

Borewit mentioned this issue Jul 22, 2024

Add support for visio sindresorhus/file-type#647

Merged

scagood mentioned this issue Jul 22, 2024

chore!: Update node versions to align with eslint v9 eslint-community/eslint-plugin-promise#484

Merged

mhassan1 mentioned this issue Jul 22, 2024

Revert "Pins node to 22.4.1 temporarily (#64)" mrhenry/polyfill-library#65

Merged

mhassan1 added a commit to mrhenry/polyfill-library that referenced this issue Jul 22, 2024

Revert "Pins node to 22.4.1 temporarily (#64)" (#65)

ad74160

This PR reverts #64, since nodejs/node#53902 has been resolved in [Node.js 22.5.1](https://nodejs.org/en/blog/release/v22.5.1).

cooderl mentioned this issue Jul 23, 2024

服务迁移中！！ cooderl/wewe-rss#202

Closed

anna-parker added a commit to loculus-project/loculus that referenced this issue Jul 23, 2024

Revert "Temporarily downgrade node until nodejs/node#53902 fix is in …

1857114

…a patch.…" This reverts commit d2832db.

anna-parker mentioned this issue Jul 23, 2024

Revert "fix(ci): Temporarily downgrade to node v22.4.1 until node v22.5 is patched." loculus-project/loculus#2325

Merged

anna-parker added a commit to loculus-project/loculus that referenced this issue Jul 23, 2024

Revert "Temporarily downgrade node until nodejs/node#53902 fix is in …

29536ae

…a patch.…" (#2325) This reverts commit d2832db as node v22.5 is now patched

github-merge-queue bot pushed a commit to pulumi/pulumi that referenced this issue Jul 23, 2024

Revert "Pin node to 22.4.x to workaround breakage" (#16731)

044e446

Reverts #16709 The underlying issue has been fixed in node 20.5.1 nodejs/node#53902 Fixes #16707

cmwylie19 mentioned this issue Jul 23, 2024

Revert tests to test on latest when a new node version comes out defenseunicorns/pepr#975

Closed

mansaj mentioned this issue Jul 24, 2024

MNTOR-3391: node 22.5.1 fixes an error with npm build mozilla/blurts-server#4862

Merged

3 tasks

janishorsts mentioned this issue Aug 1, 2024

Use latest node 22.5.1 in GitHub Actions translate-agent/webapp#85

Merged

milaninfy mentioned this issue Aug 12, 2024

(npm error Exit handler never called!:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError npm/cli#7718

Closed

2 tasks

abdullahbaa5 mentioned this issue Oct 7, 2024

Locally Running Issue baptisteArno/typebot.io#1825

Closed

jsbmg mentioned this issue Oct 21, 2024

[BUG] npm install will randomly hang forever and cannot be closed when this occurs npm/cli#4028

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Node 22.5.0 started to crash and hangs on different cases #53902

Node 22.5.0 started to crash and hangs on different cases #53902

zloirock commented Jul 17, 2024 •

edited

Loading

RedYetiDev commented Jul 17, 2024

cjihrig commented Jul 17, 2024

RedYetiDev commented Jul 17, 2024 •

edited

Loading

merceyz commented Jul 17, 2024

RedYetiDev commented Jul 17, 2024

anonrig commented Jul 17, 2024

anonrig commented Jul 17, 2024

RedYetiDev commented Jul 17, 2024 •

edited

Loading

anonrig commented Jul 17, 2024

targos commented Jul 17, 2024

anonrig commented Jul 17, 2024

merceyz commented Jul 17, 2024

merceyz commented Jul 17, 2024 •

edited

Loading

This comment has been minimized.

RedYetiDev commented Jul 17, 2024

anonrig commented Jul 17, 2024 •

edited

Loading

latin-1 commented Jul 17, 2024

anonrig commented Jul 17, 2024

merceyz commented Jul 17, 2024

nicomsz commented Jul 19, 2024

melroy89 commented Jul 19, 2024

trivikr commented Jul 19, 2024 •

edited

Loading

Node 22.5.0 started to crash and hangs on different cases #53902

Node 22.5.0 started to crash and hangs on different cases #53902

Comments

zloirock commented Jul 17, 2024 • edited Loading

Version

Platform

What steps will reproduce the bug?

RedYetiDev commented Jul 17, 2024

cjihrig commented Jul 17, 2024

RedYetiDev commented Jul 17, 2024 • edited Loading

merceyz commented Jul 17, 2024

RedYetiDev commented Jul 17, 2024

anonrig commented Jul 17, 2024

anonrig commented Jul 17, 2024

RedYetiDev commented Jul 17, 2024 • edited Loading

anonrig commented Jul 17, 2024

targos commented Jul 17, 2024

anonrig commented Jul 17, 2024

merceyz commented Jul 17, 2024

merceyz commented Jul 17, 2024 • edited Loading

This comment has been minimized.

RedYetiDev commented Jul 17, 2024

anonrig commented Jul 17, 2024 • edited Loading

latin-1 commented Jul 17, 2024

anonrig commented Jul 17, 2024

merceyz commented Jul 17, 2024

nicomsz commented Jul 19, 2024

melroy89 commented Jul 19, 2024

trivikr commented Jul 19, 2024 • edited Loading

zloirock commented Jul 17, 2024 •

edited

Loading

RedYetiDev commented Jul 17, 2024 •

edited

Loading

RedYetiDev commented Jul 17, 2024 •

edited

Loading

merceyz commented Jul 17, 2024 •

edited

Loading

anonrig commented Jul 17, 2024 •

edited

Loading

trivikr commented Jul 19, 2024 •

edited

Loading