PyCharm 2026.1.1 Excessive Re-Indexing on Every Startup Causes High CPU Usage, 5GB+ RAM Consumption, and Severe UI Lag

Environment

• IDE: PyCharm 2026.1.1 (Build #PY-261.23567.174, built on April 27, 2026)
• Project Type: Odoo Development
• RAM: 16GB
• OS: Windows 11 (X86)
• Project Size: Medium to Large

Issue Description

Since upgrading to PyCharm 2026.1, the IDE performs a full project scanning/indexing process every time the IDE is opened or restarted.

This happens consistently when:

• opening PyCharm,
• reopening an existing project,
• or restarting the IDE.

The indexing/scanning process appears to rebuild project caches repeatedly, even when:

• there are no file changes,
• no new directories,
• no dependency updates,
• and the project was already fully indexed previously.

Observed Behavior

During startup:

• RAM usage quickly increases to 5GB+,
• CPU usage becomes very high,
• the UI becomes sluggish,
• editor interactions lag significantly,
• and overall IDE responsiveness degrades severely.

The problem is especially noticeable on large Odoo development environments with many modules and Python files.

Expected Behavior

Full project scanning/indexing should ideally occur only:

1. during the first project initialization,
2. when new files/directories are added,
3. or when dependencies/interpreter settings change.

Subsequent IDE startups should reuse persisted indexes and perform only incremental updates instead of a complete rescan.

Impact

This behavior significantly affects productivity:

• slow startup times,
• heavy system resource usage,
• degraded multitasking performance,
• and unstable development workflow on reasonably capable hardware (16GB RAM).

Additional Notes

The issue appears related to:

• repeated cache rebuilding,
• non-persistent indexing state,
• or aggressive filesystem rescanning on startup.

From monitoring system activity, the indexing subsystem seems to behave as though the project is being initialized from scratch on every launch.

Request

Please investigate:

• indexing persistence between sessions,
• unnecessary full rescans,
• cache invalidation logic,
• and potential regressions introduced in version 2026.1.

It would also be helpful to have:

• an option to limit automatic rescanning,
• more granular indexing controls,
• or improved incremental indexing behavior for large Python/Odoo projects.

Thank you.