ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #intellij
Learn how to diagnose and fix IntelliJ IDEA indexing stalls, UI freezes, and JVM memory pressure using a structured diagnostic mapping and resolution path.
Learn how to define a Live Template that expands 'logd' into a SLF4J logger statement, with steps, limits and verification tips.
Stop panicking over uncommitted code loss. Learn how to use IntelliJ IDEA's Local History to recover deleted files and audit changes that Git never saw.
If IntelliJ IDEA appears to return stale build cache results after a dependency version change, the goal is to verify whether the cache is incorrectly reusing outdated outputs. The investigation should avoid clearing the entire cache or disabling the feature, focusing instead on inspecting cache keys, input timestamps, and task up‑to‑date checks. Uncertainty
Goal is to reduce resource usage for a low-traffic development workload using IntelliJ IDEA Power Save Mode. The decision is whether the mode provides a predictable cost reduction while keeping essential editing usable. Planning material references Power Save Mode in the context of background activity reduction, but the exact boundary between suppressed and
Goal: determine if enabling automatic heap dump on OutOfMemoryError in IntelliJ IDEA provides a reliable way to capture the IDE state for diagnosing intermittent UI slowdown while the IDE runs with a fixed maximum heap size. Constraints: the IDE is launched with a fixed -Xmx limit; automatic dumps guarantee capture at the cost of ongoing disk usage and poten
Background When a large project is opened or after significant external changes, IntelliJ IDEA enters a project indexing phase. During this time the IDE builds file‑based and symbol indexes, which can temporarily disable or degrade code completion, go‑to‑declaration, and inspections. Unresolved Decision The IDE’s current behavior for user‑initiated code comp
IntelliJ IDEA maintains persistent indices and in-memory PSI structures for fast code insight. Updates are incremental and tied to VFS events and OS file system notifications. The design relies on notifications rather than polling, which creates a trade-off between freshness and resource consumption. Changes made outside the IDE, on network drives, Docker vo
Goal IntelliJ IDEA’s built‑in HTTP client must resolve proxy hosts and validate SSL certificates for plugin repositories. When a proxy host’s IP changes, the IDE should re‑resolve the hostname to avoid stale connections. Constraints & Uncertainty IntelliJ does not expose a DNS cache or a flush command; the JVM performs resolution, and the IDE’s SSL conte
gradle