Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b21fa0e

Browse files
authored
Update Other section with example exit code
Add troubleshooting steps to remediate issues with the kernel killing a process.
1 parent 55e1554 commit b21fa0e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/codeql/codeql-cli/exit-codes.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,4 +71,4 @@ Other
7171
-----
7272

7373
In the case of really severe problems within the JVM that runs ``codeql``, it might return a nonzero exit code of its own choosing.
74-
This should only happen if something is severely wrong with the CodeQL installation.
74+
This should only happen if something is severely wrong with the CodeQL installation, or a memory issue with the host system running the CodeQL process. For example, Unix systems may return `Exit Code 137` to indicate that the kernel has killed a process that CodeQL has started. One way to troubleshoot this issue is to modify your `--ram=` flag for the `codeql database analyze` step and re-run your workflow.

0 commit comments

Comments
 (0)