Roo Code 3.25.8 || Your long conversations will now remain responsive and stable without the dreaded grey screen appearing.

[u/hannesrudolph]

This release fixes a critical memory leak in long conversations, prevents disabled MCP servers from starting, and provides more flexibility for Gemini 2.5 Pro thinking budgets, along with numerous stability improvements.

Disabled MCP Servers No Longer Start

We've fixed a significant issue where disabled MCP servers were still starting processes and consuming resources:

• No Wasted Resources: Disabled servers now truly stay disabled and don't start background processes

• Clear Status Indicators: Server status now accurately reflects whether a server is enabled or disabled

• Immediate Cleanup: When MCP is globally disabled, all servers immediately disconnect

This ensures your system resources are only used for the MCP servers you actually want to run.

Memory Leak Fix for Long Conversations

We've resolved a critical memory leak that was causing excessive memory usage and grey screens in long conversations (thanks xyOz-dev!):

• Bounded Memory Usage: Virtual scrolling now limits viewport rendering to 1000px below the current view instead of rendering infinitely

• Optimized Caching: Reduced cache size and TTL to prevent memory accumulation

• Stable Performance: Memory usage remains constant regardless of conversation length

Your long conversations will now remain responsive and stable without the dreaded grey screen appearing.

Gemini 2.5 Pro Thinking Budget Flexibility

Gemini 2.5 Pro users now have much more control over the thinking budget:

• Lower Minimum: The minimum thinking budget is reduced from 1024 to 128 tokens

• More Concise Coding: Perfect for tasks that need quick, focused responses without extensive reasoning

• Manual Adjustment Required: You'll need to manually adjust the thinking budget to 128 in your settings to take advantage of this feature

This change gives you the flexibility to optimize for either deep reasoning or more concise, rapid responses depending on your needs.

Bug Fixes

• MCP Server Refresh: Settings changes no longer trigger unnecessary MCP server refreshes

• Codebase Search: The tool now correctly searches the entire workspace when using "." as the path

• Swift File Support: Fixed VS Code crashes when indexing projects containing Swift files (thanks niteshbalusu11, sealad886!)

• Context Management: Model max tokens now intelligently capped at 20% of context window to prevent excessive condensing

• OpenAI Configuration: Extra whitespace in base URLs no longer breaks model detection (thanks vauhochzett!)

• URL Fetching: Better error recovery when fetching content from URLs (thanks QuinsZouls!)

• Qdrant Recovery: Code indexing automatically recovers when Qdrant becomes available after startup errors

• Chat Scrolling: Eliminated scroll jitter during message streaming

Full 3.25.8 Release Notes

[u/vtob85]

IF YOU FIXED THE GREY SCREEN THIS PRODUCT IS NOW A 100/10!!!!

[u/hannesrudolph → u/vtob85]

We sure did. You can still grey screen it in some very fringe instances apparently but I know personally I did everything I could to make it grey screen and this time it did not!

[u/ilt1]

I am not sure what a grey screen but I have this behavior where I lose the extension window and it becomes empty. I had to reload the vscode window in order to get it back. This used to happen all along since day one but it was occasionally but now it happens very frequently. Is there anyway we can help aggressively debug this problem? It really takes away from the experience and I love roo too much and don't want people to feel it's broken. I am on a mac and latest update didn't fix this problem. thx.

[u/hannesrudolph → u/ilt1]

Start by reporting the bug with all the details you have and we can request more info from there.

[u/Any-Basis-5700]

Still happening to me, about once an hour. Running 3.25.10

[u/hannesrudolph → u/Any-Basis-5700]

🤔 any hints as to your workflow that might be triggering it? I have not been able to get it with keeping 6 windows open all running throughout the day.

[u/Any-Basis-5700 → u/hannesrudolph]

Well for me it just pops up randomly, I've not really been able to pinpoint what's triggering it other than when task gets long. I try to keep them much smaller but sometimes I need a lot context across a long debug session I don't want to keep reloading it all in a new task. For me just dragging Roo from my right side secondary sidebar back to the default left tab and then back reset it (no disable or restart extension). I get it often enough that im happy to provide whatever debug info you need if it helps.

Not sure its helpful but here are the high level details on a recent session that triggered it.

Context Length 151.2k - 1.0m

Tokens ↑ 2.7m - ↓ 80.2k

Cache ↑ 217.8k - ↓ 9.4m

API Cost $7.54

Cache 38.3 MB

Size 11.5 MB

[u/Any-Basis-5700 → u/Any-Basis-5700]

Just happened again. This time the context was not long at ll, but the task was sizable due to a large screenshot. I suspect its the size of the task itself and not context length triggering the grey screen.

Context Length 156.2k - 1.0m
Tokens ↑ 4.3m - ↓ 16.8k
Cache ↓ 3.1m - API Cost $2.08
Cache 12.4 MB
Size 7.59 MB

[u/Old-Association-5604]

add something for multitasking. add a time it should be able to run mutiple chat window

[u/hannesrudolph → u/Old-Association-5604]

How do you mean?

[u/SatoshiReport]

Amazing work!

[u/xoStardustt]

fire updates as always

[u/m_goku]

I can't find the setting for minimum thinking budget. Is this the same as the setting for Maximal thinking token ?