[BUG] Process with PID: 0 access denied as it is system idle process in Windows

[sjchoure]

Describe the bug Since the PID of system processes in Windows and Unix differ, for example, PID 0 and PID 1 in *nix are given to the Scheduler and the Init Process respectively. Note: Unix PID starts from 1 PID 0 and PID 4 in Windows are given to the System Idle Process and the Init Process respectively. Note: Windows PID starts from 4

So, the System Idle Process in Windows is generally not accessible by the userland programs not even by the administrative privileges.

To Reproduce Steps to reproduce the behavior:

1. Run the current program in Windows and the Output is as follows:

Expected behavior

1. Running the same program in *nix based OS gave the desired Output.

Additional context (Optional) The solution is to slice off the PID = 0 if present in the Processes Slice inside the memory.go file. This result in the desired output without the error as follows:

Note: We still require to "Run as an Admin" to get the desired result

[DarthBenro008]

@saviourcode i would highly suggest you add a os check (using GOOS ) and then slice of PID 0 if its windows

[sjchoure]

@saviourcode i would highly suggest you add a os check (using GOOS ) and then slice of PID 0 if its windows

Yeah, that way is more acceptable and maintainable in long run, rather than slicing random PID: 0, 😃 Okay I will make the changes.