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.

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

possible memory leak #359

Open
BreakElseHalt opened this issue Feb 3, 2025 · 3 comments
Open

possible memory leak #359

BreakElseHalt opened this issue Feb 3, 2025 · 3 comments

Comments

@BreakElseHalt
Copy link

Hi,

we get some errors working on a specific .int file.
Looks like this was already reported and fixed with #351.
I've updated to InterSystems Language Server 2.7.0 but unfortunately the error still occurs.
Can be reproduced.

<--- Last few GCs --->

[26112:00006280000F8000]   714178 ms: Mark-Compact 3915.0 (4082.5) -> 3908.7 (4082.7) MB, pooled: 6 MB, 4804.26 / 0.00 ms  (average mu = 0.072, current mu = 0.022) allocation failure; scavenge might not succeed
[26112:00006280000F8000]   717983 ms: Mark-Compact 3917.3 (4083.2) -> 3910.3 (4083.2) MB, pooled: 6 MB, 3752.92 / 0.00 ms  (average mu = 0.046, current mu = 0.014) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

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

 1: 00007FF78F7DEB5A uv_cpumask_size+56202
 2: 00007FF78F75864B node::OnFatalError+747
 3: 00007FF7928C90D4 v8::Function::NewInstance+868
 4: 00007FF7928C9043 v8::Function::NewInstance+723
 5: 00007FF792999D67 v8::CppHeap::CollectGarbageInYoungGenerationForTesting+66807
 6: 00007FF78E3A5104 v8::CppHeap::Terminate+134340
 7: 00007FF78E3A487B v8::CppHeap::Terminate+132155
 8: 00007FF791D4C75D Cr_z_adler32+5491917
 9: 00007FF790FBC444 v8::internal::ThreadIsolation::StartOfJitAllocationAt+348100
10: 00007FF790FB7912 v8::internal::ThreadIsolation::StartOfJitAllocationAt+328850
11: 00007FF790FA7A29 v8::internal::ThreadIsolation::StartOfJitAllocationAt+263593
12: 00007FF791210FEA v8::internal::StrongRootAllocatorBase::deallocate_impl+2428842
13: 00007FF791673E3A v8::internal::compiler::CompilationDependencies::FieldTypeDependencyOffTheRecord+2913434
14: 00007FF7916C7AF6 v8::internal::compiler::CompilationDependencies::FieldTypeDependencyOffTheRecord+3256662
15: 00007FF7E00B90C7 
Version: 1.96.4 (system setup)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
@isc-bsaviano
Copy link
Contributor

Hi @BreakElseHalt, thanks for reporting this. Can you send me the file that you're seeing the leak on? If you're not comfortable sharing this publicly, you can send me a direct message on the Developer Community. Does the crash occur when you open the affected file, or after editing it for some time?

@BreakElseHalt
Copy link
Author

Hi @isc-bsaviano, please excuse my late response, unfortunately I cannot provide this specific file but I'm working on a similar one to mock the behaviour.
The crash occurs while editing.
Thanks!

@isc-bsaviano
Copy link
Contributor

No worries @BreakElseHalt, I appreciate you reporting this and helping me reproduce it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants