If this is happening to you, please contact us and let us know where the disk space is being used, how much is being used, and how you are using the software.
Possible Reason for this Issue
The most likely cause of this is due to the indexing system that our protocol analyzers use for processing decoded data and making it available for search.
Specifically, analyzer_db directories are created when protocol analyzers are used in your capture. These directories will be created and can be found in the following locations:
Linux: Inside your /tmp folder
Fortunately, the analyzer_db directories are cleared upon restarting the software. Though if you leave the software open for long periods of time, the search indexing system does not delete these analyzer_db directories.
In cases where you plan on capturing large amounts of data (greater than 1 hour), we recommend the following workaround to have more control over the disk space used during captures:
Save a preset with your protocol analyzer added with your preferred settings
Remove all protocol analyzers before starting your capture
Start your capture
Once the capture is complete, save the capture to ensure that you keep your data in case anything goes wrong.
Load your preset to begin decoding the data
Restart the app before starting a new capture (to clear the analyzer_db directories)
Instructions for saving/loading a preset and saving captures can be found below.