menu_book

Knowledge Base

Documentation, guides, and resources for Noldus products.

After recording for a long time, the TrackLab system becomes non-responsive with high memory and CPU load.

Last updated: Aug 24, 2026

The cause of this problem is variable.

  1. Get the log files "C:\ProgramData\Noldus\TrackLab\2\Log", "C:\ProgramData\Noldus\TrackLab Recorder\2\Log" and "C:\ProgramData\Noldus\TrackLab Server\2\Log"
  2. Get R&D assistance and share the log files.
  3. If R&D finds no issues in the logs: (a) stop recording, reboot the PC and restart recording. This is a temporary solution. For the long-term: (b) recommend the user to apply a time interval of max 1 week for replaying data, viewing and exporting analysis results. Alternatively, (c) the user may opt to reduce the recording session duration (occasionally stopping-restarting recording). Note: raw data export is not affected by this performance bottleneck and can be exported for bigger time windows.
  4. Note: the product roadmap includes hardware merging, i.e. selecting 1 higher performance PC to replace the current TrackLab PC and Sewio server PC. R&D aims to increase data processing performance with this improvement. Ask the Product Manager for more details.

shopping_bag
check_circle

Thank you!

We'll get back to you shortly.

error

Please correct the following errors:

error

error

error

error

By clicking Submit, you consent to Noldus processing your data as described in our privacy policy.

check_circle

Thank you for registering!

We look forward to seeing you at the NoldusViso launch event.

error

Please correct the following errors:

error

error

error

error

error

By clicking Register, you consent to Noldus processing your data as described in our privacy policy.