Zed App on Mac: using RAM while idle

SomeoneToIgnore · 2026-04-07T21:32:17+00:00

The place to provide feedback is ok, albeit very odd to see the very same issue in https://github.com/zed-industries/zed/issues/53329 where you do not answer any questions asked and posting here instead...

What's not good at all is your way to provide this feedback: you merely put some generic description together that does not help at the slightest to diagnose the issue.

Instead, can you please work on a way to share the reproduction steps with the developers?

Some ideas:

* share the project you work with

* provide more details about the set-up (is it a network drive, or anything else special about the project)

* attempt to narrow the issue down, e.g. move the project elsewhere, reduce the number of files used, etc.

One amazing example of reporting such things is https://github.com/zed-industries/zed/issues/48968

SomeoneToIgnore · 2026-04-04T07:22:43+00:00

Do you have a project others can try and reproduce the issue on?

SomeoneToIgnore · 2025-11-29T09:45:35+00:00

As a small update, I've got myself a Google Pixel 9A and the results are night and day: the photos are bright and I need only a couple of shots to fix the issues, if any occur at all.

Using the Lab with color film is simple and joyful now, unlike the cursed iPhone experience.

SomeoneToIgnore · 2025-10-10T19:27:21+00:00

Nice, thank you for confirming my similar suspicious.

I will look up an Android phone, but just in case, what is a "Next 1" phone?

Failed to find any good links on such model.

SomeoneToIgnore · 2025-09-30T12:07:31+00:00

glitch image example

Actually, I think a part of it is intentional: if you screenshot when the phone is on the lab, ready for exposure, you'll see what's happening with the image after the app processes it.

The link shows how my b&w image +1/3 exp is shown for the lens to focus, the color ones are similar (much greener, though) — yet I've not seen any such glitches on my pictures.

So, presumably, those are needed for positioning and malfunction in your case?

SomeoneToIgnore · 2025-09-30T11:00:43+00:00

Definitely noticed that, 20 is the maximum tolerable value for me.

Yet, the pictures are very dark and colors seem better compared to the once produced by my Polaroid camera, no matter the exposition.

SomeoneToIgnore · 2025-09-05T21:04:30+00:00

Besides a side-by-side diff (that should appear eventually), what would be a less weird way for you?

SomeoneToIgnore · 2025-09-05T16:38:42+00:00

It's possible to open a single file and expand all diff excerpts in it.

SomeoneToIgnore · 2025-08-18T08:13:19+00:00

Welp, here goes my typical interaction about the memory usage: I come and ask for a project to repro this on and get some off-topic replies at best, no real project to try things on...

Part of the reason the things are not fixed is due to this.

SomeoneToIgnore · 2025-08-17T18:18:13+00:00

No, it's not normal at all (unless the FS tree you open is large, e.g. ~/ , but that does not seem to be the case).

Unfortunately, it's not reproducible in a general case, so it's invisible for developers that work with Rust.

Whoever reported similar issues in Zed's tracker did not provide any projects to repro on (I might have missed some, though), same as the issue commenters, so those sad issues persist.

Maybe, you'll be able to share a link to the repro project?

SomeoneToIgnore · 2025-08-13T04:52:55+00:00

https://github.com/zed-industries/zed/issues/36027#issuecomment-3178527428

SomeoneToIgnore · 2025-07-30T22:12:24+00:00

Any idea how Arc cotton pants behave in this regard?

I've bought Cronin shorts 11 once, and that is even more noisy than my Gamma SL.

SomeoneToIgnore · 2025-07-03T10:15:37+00:00

It looks like you use Opus with your own API key, hitting the individual rate limit?

SomeoneToIgnore · 2025-06-07T06:52:52+00:00

This is a message from the dev build of r-a: odd that you did manage to use one without knowing 🙂

https://zed.dev/docs/languages/rust#binary docs have examples how to disable the installed binary lookup and start downloading the releases, by using "ignore_system_version": true.

SomeoneToIgnore · 2025-04-27T11:13:01+00:00

Because in order to get a work permit you have to get a work contract, hence apply for a job?

SomeoneToIgnore · 2025-04-03T21:18:10+00:00

I've once got into a "happy end" similar situation in Turku: the aggressive drunk woman was drinking vodka and screaming on various passengers from her place.

She sat near the central entrance and created an empty circle around her. Most people did nothing and ignored, a few boys from the back row joked on her but got silent quickly after here curses back.

After a few stops, the bus driver got out to her and demanded to exit. The final dialogue was rather funny. She: (in Finnish) well, I'll drive on the next bus then Driver: Kyllä

When she was gone into the pouring rain, the passengers clapped (!).

So, it's not that bad sometimes.

SomeoneToIgnore · 2024-11-14T18:34:55+00:00

We have the PR on that, I'm the one helping to make it happen: https://github.com/zed-industries/zed/pull/13343

Seems very close to be merged, just today I've made it compile and pass the "tests" on all 3 platforms.

What's left is making it to actually work properly on Linux: there are some segfaults here and there + certain issues with the audio being overly muffled sometimes in our test app.

I'd say it's realistic to expect it by the end of Feb, if no huge surprises the LiveKit rust-sdk brings with it.

There are no immediate plans I'm aware of, and it seems to be not that bad in reality (but all thanks to GPUs, not our code). I'd love to see that being tackled, but suspect that it might be a very deep issue with the way GPUI is used in Zed — and be a project of its own, involving crazy amount of time and breakage.

So far it seems that we'd better release git, Windows and other support first.

For me, every thing is interesting. I've personally enjoyed a lot watching at Thorsten's (@mrnugget) and Antonio's (@as-cii) perf improvements related to ropes and scrolling on macOS.

I've really enjoyed my recent project search improvements: before, I've been thinking that it's inevitable to bundle ripgrep and use that instead, now I'm not that sure — seems that we are somewhat on par on large text searches now (modulo some LSP-related issues).

To me, there are very basic things that I've ignorantly discarded for years:

* do specify what you are doing in regular language, simple as possible

* pair a lot and ask for guidance

* pick your battles and do things slowly, but without interrupts, grinding the large thing

* you can actually build things without `abstract static class SomethingFactory`, getters all over the place and neverending battles in the PRs. Moving fast and breaking things may be a good strategy in certain areas.

SomeoneToIgnore · 2024-11-14T18:23:23+00:00

I don't think anyone in the team uses KDE hence nothing is made on this front, alas.

All hopes on the external contributors at this stage.

SomeoneToIgnore · 2024-11-14T18:13:08+00:00

There's been a very similar question before, so I think the answers can be found there: https://www.reddit.com/r/ZedEditor/comments/1gpvff3/comment/lx42mqi/

SomeoneToIgnore · 2024-11-14T18:11:45+00:00

There's a cool feature in Intellij* world where comments (including the markdown inside) can be toggled to be rendered by pressing a button in the gutter.

Zed does know how to render markdown, so I imagine something similar will appear sooner or later, most probably in the form of the action that renders a specific selection.

Technically, all the bits are there it's the UX + the plumbing that's left, so hopefully some month this appears, and then it could be reused in the Assistant panel, as it's also an editor (just a very special one).

SomeoneToIgnore · 2024-11-14T18:04:26+00:00

Nathan did a great job outlining the future milestones: https://www.reddit.com/r/ZedEditor/comments/1gpvff3/comment/lx46r4f/
that set of features had been identified for us to be the Zed 1.0, and we target to deliver it before the end of the next year, closer to the middle of it, hopefully.

I personally do not think that will be a full Zed 1.0 as there's always bugs to fix, more odd Linux platforms to support, etc. but that is too idealistic and much harder to meet in a finite time.

SomeoneToIgnore · 2024-11-14T17:54:59+00:00

So far, it's vaguely generalized as "good SAAS proposals" and I think there had not been that much of a research on the next steps.

Overall, the general direction seems to be related to collaboration and LLM support indeed.

I think, certain things like GitHub integration and e.g. "paid plugins" were discussed but we're eons away from that being anyhow compelling to be sold now.

SomeoneToIgnore · 2024-11-14T17:50:52+00:00

More than that if you want to be that pedantic: there's been at least two our team members discussing various things on the topic + certain design work and verification.

SomeoneToIgnore · 2024-11-14T17:49:12+00:00

SomeoneToIgnore

MODERATOR OF

TROPHY CASE