releasing memory in apply diff

[xyOz-dev]

Related GitHub Issue

Closes: nothing, simply a memory optimization to avoid greyscreens.

Description

This PR addresses a potential memory leak in the applyDiffTool by explicitly releasing the originalContent buffer after it's used for diff application.

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.

---

Important

Optimize memory usage in applyDiffTool by releasing originalContent after use.

• Memory Optimization:
  • In applyDiffTool function in applyDiffTool.ts, release originalContent variable by setting it to null after diff application to prevent memory leaks.

^{This description was created by for 95c005b. You can customize this summary. It will automatically update as commits are pushed.}

[daniel-lxs]

Hey @xyOz-dev , thank you.

I think this is done by the GC automatically however I don't think it hurts to have this either.

Have you seen any other instances of this on other tools?

[xyOz-dev]

Hey @xyOz-dev , thank you.

I think this is done by the GC automatically however I don't think it hurts to have this either.

Have you seen any other instances of this on other tools?

This simply speeds it up, when we use multiple instances of roo frequently firing this tool it quickly becomes a large issue. so instead of waiting 600-800ms between gc runs, we clear the memory in 50ms or less

i havent gotten through all the tools yet as im busy with family, will look more during the week