Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

incorrect outofmemory death

Open
#21,543 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
cli, devtools

Research direction

Reproduce the reported CodeQL query command with --ram 10240 and capture the memory-related output. Trace how the CLI passes --ram to query evaluation and how the Java heap maximum is selected. Done when the discrepancy is explained and the error reports the relevant configured limit or the behavior is corrected.

Written by the indexing model from the issue text.

Description

I run a query like this:

../../sources/codeql/codeql query run ./queries/types-flow.ql -d ../../sources/linux-6.12.74/linux-db/ -j0 --ram 10240 > ./results/types-flow.txt

I get

types-flow.ql: [1/1 eval 4m37s] Failed: Query evaluation ran out of Java heap (Java heap maximum: 2070 MiB).
(eventual cause: OutOfMemoryError "Java heap space")
CodeQL is out of memory. Try increasing the memory available to CodeQL using the --ram option.
make: *** [Makefile:44: types-flow] Error 99

Clearly I passed 10GB to --ram, why does the error message say that the java heap maximum is 2GB?

Dominant language
CodeQL
Stars
10.1k
Forks
2.1k
Avg merge
2d 16h
Merged PRs (30d)
143

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/codeql

All issues in github/codeql

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.