Skip to content

Capturing a Process Memory Dump

If the SenseOn agent is showing abnormally high memory usage and a service restart is not resolving it, a process memory dump gives the support team a snapshot of what is held in memory at that moment. This helps confirm whether a memory leak is present and, if so, which part of the agent is responsible.

Send the dump file to support@senseon.io together with the agent version information below.

⚠ File size: A full process memory dump will typically be several hundred megabytes. It is too large to send by email — please upload it via the file sharing method provided by your support contact, or attach it to your open support case.

Windows

Step 1: Identify the process

Open an elevated PowerShell window and run:

Get-Process senseon* | Select-Object Name, Id, WorkingSet64, PrivateMemorySize64

Note the Id of the process with the elevated Working Set — this is the PID you will use in the next step.

Step 2: Create the dump

Option A — Task Manager

  1. Open Task Manager and go to the Details tab.
  2. Right-click the senseon-seed.exe process (or whichever senseon-* process has the elevated Working Set).
  3. Select Create memory dump file.
  4. The dialog will show you where the .dmp file was saved (typically C:\Users\<username>\AppData\Local\Temp\).

Option B — Sysinternals ProcDump

If Task Manager is unavailable or the system is too low on memory to open it, use ProcDump from Sysinternals:

procdump -ma <PID> C:\Temp\senseon-agent.dmp

Replace <PID> with the process ID from Step 1. The -ma flag captures a full memory dump rather than a minidump.

Step 3: Gather version information

Run the following and include the output in your support message:

Get-Process -Id <PID> | Select-Object Name, Id, WorkingSet64, PrivateMemorySize64, VirtualMemorySize64
Get-Content "C:\Program Files\senseon-see\version.txt"

Linux

Step 1: Identify the process

ps aux | grep senseon-seed

Note the PID (second column) of the senseon-seed process.

Step 2: Create the dump

Install gcore if not already available (it is part of gdb):

sudo apt-get install gdb   # Debian/Ubuntu
sudo yum install gdb       # RHEL/CentOS

Then capture the dump:

sudo gcore -o /tmp/senseon-seed.core <PID>

Step 3: Gather version information

ps -p <PID> -o pid,vsz,rss,comm
cat /etc/senseon-see/version.txt

macOS

Step 1: Identify the process

ps aux | grep senseon

Note the PID of the process with high memory usage.

Step 2: Create the dump

sudo gcore -o /tmp/senseon.core <PID>

Step 3: Gather version information

ps -p <PID> -o pid,vsz,rss,comm
cat /var/senseon-see/version.txt