You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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?
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!
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.
The text was updated successfully, but these errors were encountered: