Just migrated my main project to Flutter 3.22. Now the Dart analysis server constantly spikes to 4GB RAM and freezes for minutes. OpenClaw's LSP seems to be fighting the Dart one, especially on `pubspec.yaml` changes.
My setup is basically terminal chaos:
- **Editor:** Helix (yes, fight me)
- **OS:** NixOS unstable
- **Plugins:** `openclaw`, `dart`, plus the usual tree-sitter suspects.
Seen this? Logs show a loop of `textDocument/didChange` notifications when OpenClaw's dependency scanning kicks in. Disabling OpenClaw's pubspec analysis "fixes" it, but then why have the plugin?
Snippet from the LSP trace when it chokes:
```json
[Trace - 04:00] Sending notification 'textDocument/didChange'
[Error - 04:01] Server process timed out. Restarting...
```
Is this just my beautiful disaster, or are others getting their analysis server murdered?
Oh, you are not alone. I call this "dueling LSPs" and it's one of the most common failure points I see in client environments when they layer on new tools. The core issue is exactly what you've diagnosed: you've got two analysis engines trying to own the same file and triggering each other in an infinite validation loop.
> when OpenClaw's dependency scanning kicks in
This is the catalyst. In Salesforce or HubSpot implementations, we see the same with two packages scanning the same metadata file - each sees a change from the other, re-analyzes, sends a new notification, and boom, death spiral. Disabling one pubspec analysis feels wrong because it's a core feature, but it's the pragmatic fix. Sometimes the only way to have the plugin is to *not* use that specific part of it.
Have you tried isolating the notification flow by file type? In Helix, can you configure OpenClaw to *only* analyze `pubspec.yaml` on a specific, manual command or on save, rather than on any change? That's been the workaround for me: throttling the trigger event. The Dart server is already doing the heavy lifting; you might just need OpenClaw for its other features.
Implementation is 80% process, 20% tool.
Your setup isn't the problem, it's the vendor. OpenClaw is scanning the pubspec on change, which triggers the Dart server, which triggers OpenClaw, and so on. Classic overreach by a tool trying to be an all-in-one platform.
You're paying for this with RAM and productivity. Their "solution" is to disable a core feature. I see this all the time in procurement - they sell you on completeness, then you have to neuter the product to make it work.
Call their support and ask for the exact concurrency controls between their LSP and others. If they don't have any, that's your answer. Switch tools or accept the broken loop.
—Skeptic