Error running analysis for cpp: Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.23.5/x64/codeql/codeql database run-queries --ram=14581 --threads=4 --expect-discarded-cache /home/runner/work/_temp/codeql_databases/cpp --min-disk-free=1024 -v". Exit code was 100 and error was: Oops! A fatal internal error occurred. Details: com.semmle.util.exception.CatastrophicError: An error occurred while evaluating _IRType::IRIntegerType#8fa2139a_IRType::TIRAddressType#19c58860_Instruction::LoadInstruction.getSour__#shared/1@ffd770vm Severe disk cache trouble (corruption or out of space) at /home/runner/work/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/5a/3f.pack: Failed to write item to disk The RA to evaluate was: {1} r1 = SCAN cached_IRType::TIRAddressType#19c58860 OUTPUT In.1 {1} | JOIN WITH `SSAConstruction::getInstructionResultIRType/1#bdc4ce95_10#join_rhs` ON FIRST 1 OUTPUT Rhs.1 {1} r2 = SCAN IRType::IRIntegerType#8fa2139a OUTPUT In.0 {1} | STREAM DEDUP {1} | JOIN WITH `SSAConstruction::getInstructionResultIRType/1#bdc4ce95_10#join_rhs` ON FIRST 1 OUTPUT Rhs.1 {1} r3 = r1 UNION r2 {1} r4 = JOIN r3 WITH project#Instruction::FieldAddressInstruction#ba88e7bc ON FIRST 1 OUTPUT Lhs.0 {1} r5 = JOIN r3 WITH project#Instruction::PointerArithmeticInstruction#2027e36d ON FIRST 1 OUTPUT Lhs.0 {1} r6 = JOIN r3 WITH project#Instruction::VariableAddressInstruction#60de476a ON FIRST 1 OUTPUT Lhs.0 {1} r7 = JOIN r3 WITH Instruction::PhiInstruction#6acf712e ON FIRST 1 OUTPUT Lhs.0 {2} r8 = JOIN r3 WITH `Instruction::LoadInstruction.getSourceAddress/0#dispred#fb07cec8` ON FIRST 1 OUTPUT Rhs.1, Lhs.0 {1} r9 = JOIN r8 WITH project#Instruction::FieldAddressInstruction#ba88e7bc ON FIRST 1 OUTPUT Lhs.1 {1} r10 = JOIN r8 WITH project#Instruction::VariableAddressInstruction#60de476a ON FIRST 1 OUTPUT Lhs.1 {2} r11 = JOIN r3 WITH `SSAConstruction::getInstructionOpcode/2#3bb281a5_10#join_rhs` ON FIRST 1 OUTPUT Rhs.1, Lhs.0 {1} | JOIN WITH num#Opcode::TCall#26192cd8 ON FIRST 1 OUTPUT Lhs.1 {2} r12 = JOIN r3 WITH `Operand::Operand.getAnyDef/0#dispred#8dbe2fb8_10#join_rhs` ON FIRST 1 OUTPUT Rhs.1, Lhs.0 {1} r13 = JOIN r12 WITH Operand::AddressOperand#4cc35f39 ON FIRST 1 OUTPUT Lhs.1 {1} r14 = JOIN r3 WITH project#Instruction::VariableInstruction#bd9aecac ON FIRST 1 OUTPUT Lhs.0 {2} | JOIN WITH `SSAConstruction::getInstructionOpcode/2#3bb281a5_10#join_rhs` ON FIRST 1 OUTPUT Rhs.1, Lhs.0 {1} | JOIN WITH num#Opcode::TInitializeParameter#f85cc1a9 ON FIRST 1 OUTPUT Lhs.1 {2} r15 = JOIN r12 WITH cached_Operand::RegisterOperand#70a4cccc ON FIRST 1 OUTPUT Rhs.1, Lhs.1 {1} | JOIN WITH OperandTag::ArgumentOperandTag#14a83a82 ON FIRST 1 OUTPUT Lhs.1 {1} r16 = r4 UNION r5 UNION r6 UNION r7 UNION r9 UNION r10 UNION r11 UNION r13 UNION r14 UNION r15 {1} | JOIN WITH `cached_ValueNumberingInternal::tvalueNumber/1#f03b58f9` ON FIRST 1 OUTPUT Rhs.1 return r16 (eventual cause: IOException "No space left on device") at com.semmle.inmemory.pipeline.MetaPipelineInstance.wrapWithRaDump(MetaPipelineInstance.java:212) at com.semmle.inmemory.pipeline.MetaPipelineInstance.exceptionCaught(MetaPipelineInstance.java:182) at com.semmle.inmemory.scheduler.execution.ThreadableWork.handleAndLog(ThreadableWork.java:593) at com.semmle.inmemory.scheduler.execution.ThreadableWork.doSomeWork(ThreadableWork.java:410) at com.semmle.inmemory.scheduler.IntensionalLayer$IntensionalWork.evaluate(IntensionalLayer.java:134) at com.semmle.inmemory.scheduler.SimpleLayerTask$SimpleLayerWork.doWork(SimpleLayerTask.java:78) at com.semmle.inmemory.scheduler.execution.ThreadableWork.doSomeWork(ThreadableWork.java:396) at com.semmle.inmemory.scheduler.execution.ExecutionScheduler.runnerMain(ExecutionScheduler.java:713) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Cause

CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/