Skip to main content
This guide walks through diagnosing and resolving the most common issues you’ll encounter with Memvid.

Quick Diagnosis

Run these commands to quickly identify issues:

Common Issues

”File is locked” when opening

  • FileLocked: File is locked by another process
  • Operations hang indefinitely
  • Cannot open file in Python/Node.js
  1. Wait for the other process to finish
  2. Kill the blocking process (if stuck):
  3. Open in read-only mode:
  4. Check for crashed processes - if a process crashed while holding a lock, restart your terminal/IDE

Search returns no results

  • mem.find() returns empty results
  • CLI search shows “0 results”
  • Expected documents not appearing
  1. Verify content exists:
  2. Check search mode - try lex for exact matches, sem for semantic:
  3. Rebuild indices if they’re corrupted:
  4. Check embeddings were enabled during ingestion:

“CapacityExceeded” error

  • CapacityExceeded: Memory file exceeded capacity limit
  • put() operations fail
  • Cannot add new content
  1. Upgrade your plan for more capacity:
  2. Delete old content:
  3. Vacuum to reclaim space:
  4. Archive and create new file:

Slow query performance

  • Queries taking >100ms
  • Timeouts on large files
  • High memory usage during search
  1. Reduce k value for fewer results:
  2. Use specific search mode:
  3. Add scope filters:
  4. Enable vector compression for smaller index:
  5. Split into multiple files for very large datasets:

Import errors in Python

  • ImportError: cannot import name 'use' from 'memvid_sdk'
  • ModuleNotFoundError: No module named 'memvid_sdk'
  • ImportError: libmemvid.so not found
  1. Install/reinstall the SDK:
  2. Check Python version (requires 3.8+):
  3. Use correct virtual environment:
  4. On Apple Silicon, ensure you’re using native Python:

Native binding errors in Node.js

  • Error: Cannot find module '../index.node'
  • Error: The module was compiled against a different Node.js version
  • Segmentation fault on import
  1. Reinstall with rebuild:
  2. Check Node.js version (requires 18+):
  3. Install build tools if needed:

File corruption after crash

  • CorruptFile: Invalid header magic bytes
  • VerificationFailed: Checksum mismatch
  • File won’t open after system crash
  1. Run the doctor command:
  2. Rebuild indices:
  3. If recovery fails, restore from backup:
  4. Prevent future corruption:
    • Always call mem.seal() before exiting
    • Use UPS/battery backup for critical systems
    • Enable automatic backups

Framework adapter not working

  • mem.tools returns empty or None
  • Framework-specific methods missing
  • Type errors with framework objects
  1. Install the framework dependency:
  2. Use correct adapter name:
  3. Check framework version compatibility:

Diagnostic Commands

Full Health Check

Performance Profile


Still Having Issues?

Error Reference

Complete error code documentation

GitHub Issues

Search existing issues or report new ones

Discord Community

Get real-time help from the community

Email Support

Contact our support team