system_info table reporting -1 as physical memory on Windows Server
Open
Nobody has claimed this yet.
bug
triage
virtual tables
Windows
- Dominant language
- C++
- Stars
- 23.6k
- Forks
- 2.6k
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 14
Description
Bug report
What operating system and version are you using?
Windows Server
What version of osquery are you using?
osqueri 5.7.0
What steps did you take to reproduce the issue?
select physical_memory from system_info;
What did you expect to see?
actual ram value
What did you see instead?
-1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the system_info table and reproduce SELECT physical_memory FROM system_info; on Windows Server. Trace how that table obtains physical memory and verify the result against the host's actual RAM; done means it reports the actual value instead of -1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100