CodeQL Analysis crash with out of memory
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 25/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- github-actions, typescript
研究方向
從連結的 CodeQL Actions 執行記錄以及 packages/gizmo/ts/define.define_deps.spec.ts 的擷取失敗開始。將其與 type-plus 的 pull request 範例和已回報的 spec 檔案 workaround 進行比較;當 TypeScript CodeQL 分析在 parser 未耗盡記憶體的情況下完成,或已清楚記錄支援的 workaround 時,即表示完成。
由索引模型根據 Issue 內容生成。
描述
https://github.com/unional/async-fp/actions/runs/4653860071/jobs/8235098420
[2023-04-10 02:21:17] [build-stdout] Extracting /home/runner/work/async-fp/async-fp/packages/gizmo/ts/define.define_deps.spec.ts
[2023-04-10 02:43:15] [build-stderr] <--- Last few GCs --->
[2023-04-10 02:43:15] [build-stderr] [2032:0x6de5530] 1319634 ms: Mark-sweep 3160.3 (3390.9) -> 3143.5 (3389.8) MB, 2799.8 / 0.0 ms (average mu = 0.119, current mu = 0.046) allocation failure; scavenge might not succeed
[2023-04-10 02:43:15] [build-stderr] [2032:0x6de5530] 1319773 ms: Scavenge 3159.3 (3389.8) -> 3144.1 (3389.8) MB, 20.2 / 0.0 ms (average mu = 0.119, current mu = 0.046) allocation failure;
[2023-04-10 02:43:15] [build-stderr] <--- JS stacktrace --->
[2023-04-10 02:43:15] [build-stderr] FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
[2023-04-10 02:43:15] [build-stderr] 1: 0xb7b3e0 node::Abort() [node]
[2023-04-10 02:43:15] [build-stderr] 2: 0xa8c8aa [node]
[2023-04-10 02:43:15] [build-stderr] 3: 0xd69100 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
[2023-04-10 02:43:15] [build-stderr] 4: 0xd694a7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
[2023-04-10 02:43:15] [build-stderr] 5: 0xf46ba5 [node]
[2023-04-10 02:43:15] [build-stderr] 6: 0xf47aa8 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]
[2023-04-10 02:43:15] [build-stderr] 7: 0xf57fb3 [node]
[2023-04-10 02:43:15] [build-stderr] 8: 0xf58e28 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
[2023-04-10 02:43:15] [build-stderr] 9: 0xf3378e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
[2023-04-10 02:43:15] [build-stderr] 10: 0xf34b57 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
[2023-04-10 02:43:15] [build-stderr] 11: 0xf15d2a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
[2023-04-10 02:43:15] [build-stderr] 12: 0x12dacdf v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
[2023-04-10 02:43:15] [build-stderr] 13: 0x1707b79 [node]
[2023-04-10 02:43:16] [build-stderr] Exception while extracting /home/runner/work/async-fp/async-fp/packages/gizmo/ts/define.define_deps.spec.ts.
[2023-04-10 02:43:16] [build-stderr] The TypeScript parser wrapper crashed, possibly from running out of memory.
[2023-04-10 02:43:16] [build-stderr] at com.semmle.ts.extractor.TypeScriptParser.getExceptionFromMalformedResponse(TypeScriptParser.java:413)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.ts.extractor.TypeScriptParser.talkToParserWrapper(TypeScriptParser.java:381)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.ts.extractor.TypeScriptParser.parse(TypeScriptParser.java:451)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.TypeScriptExtractor.extract(TypeScriptExtractor.java:24)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.FileExtractor.extractContents(FileExtractor.java:547)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.FileExtractor.extract(FileExtractor.java:454)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.doExtract(AutoBuild.java:1234)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.extract(AutoBuild.java:1220)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.extractTypeScriptFiles(AutoBuild.java:1173)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.extractTypeScript(AutoBuild.java:1051)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.extractSource(AutoBuild.java:752)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.run(AutoBuild.java:459)
[2023-04-10 02:43:16] [build-stderr] at com.semmle.js.extractor.AutoBuild.main(AutoBuild.java:1329)
Error: 4-10 02:43:16] [ERROR] Spawned process exited abnormally (code 1; tried to run: [/opt/hostedtoolcache/CodeQL/2.12.6-20230403/x[64](https://github.com/unional/async-fp/actions/runs/4653860071/jobs/8235098420#step:5:65)/codeql/javascript/tools/autobuild.sh])
This tends to happen on TypeScript project.
I have also seen this on type-plus
And a workaround is to ignore the spec files.
- 主要語言
- TypeScript
- 星號
- 1.6k
- 分支
- 493
- 平均合併
- 1 天 10 小時
- 30 天內合併 PR
- 52
環境準備
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/codeql-action 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
github/codeql-action#4052 · 4 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 48/100
github/codeql-action#4173 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 45/100
github/codeql-action#4078 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 48/100
github/codeql-action#4008 · 9 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 52/100
github/codeql-action#3978 · 4 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
查看 github/codeql-action 的全部 Issue
相似的 Issue
-
check:passed streams:add
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
Fission-AI/OpenSpec#1986 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
nestjs/docs.nestjs.com#3554 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
publicodes/publicodes#868 ·
-
namespace operations
難度 1/5 1 小時以內 新手友好度 78/100
EclipseFdn/open-vsx.org#13488 ·
維護者通常 2 天內回覆