🐞 Dagger: runtime: out of memory

[lyzhang1999]

What is the issue?

I have written some of my own CUE Modules, which may go out of memory when run multiple times over a long period of time.

Log output

Steps to reproduce

No response

Dagger version

dagger devel (b32c873) linux/amd64

OS version

Linux VM-0-6-ubuntu 4.15.0-159-generic #167-Ubuntu SMP Tue Sep 21 08:55:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

[grouville]

Hello,
Thanks for the issue. Can you please paste your docker Resources info ? My instinct tells me that you go out of memory in the docker daemon scope

[lyzhang1999]

but in dagger 0.1 API and dagger 0.1 version there is no such problem. when I upgrade dagger 0.2 and migrate some cue module to 0.2 API, sometimes it happen. and when I use Dagger 0.2, It seem calculating DAG becomes very slow, I use same machine.
It seems there is memory problem with dagger 0.2

[grouville]

. when I upgrade dagger 0.2 and migrate some cue module to 0.2 API, sometimes it happen. and when I use Dagger 0.2, It see

Ok. We'll need access to a repro case (even privately) in order to isolate the root cause. Could you please send us a Gist ?

It seem calculating DAG becomes very slow

Do you mean with a cue eval ?

• By the way, if I recall well, we already had an issue in the past and it was related to an upstream update of one of a bash package in a Plan that leaked. We might however, have an issue and it's possible that the root cause is dagger related.

Thanks for highlighting it, can't wait to isolate the root cause 😇

[lyzhang1999]

I'll provide another clue and we can discuss the repository access issue later.

You can see dagger use 13.06G memory.
Device: Macbook M1 Pro
Dagger Version: v0.2.4
OS: macOS Monterey

[jlongtine]

I could be wrong, but this sounds like a CUE evaluation issue. There are some cases that cause the CUE evaluator to blow up and chew through RAM. I agree with @grouville about creating a repro (including looking at the actual CUE causing this -- privately) and figuring out what is going on.

@grouville Feel free to pull me in, if you're getting stumped on this.

One thing to try: cue eval the config. That should help us narrow it down.

[grouville]

looking

Yes with pleasure @jlongtine. I'm currently waiting for their repro case 😇

Easier that way: @lyzhang1999, whenever you have a repro, could you please share it to both of us ?

I could be wrong, but this sounds like a CUE evaluation issue

That's what I thought yes. Let's see whenever it's ready 😇

[lyzhang1999]

have we got any new information?

[captainroy-hy]

have we got any new information?

maybe it's related to this issue
It was involved in v0.3.0-alpha4 and has been fixed in v0.4.3-beta.1.

[lyzhang1999]

have we got any new information?

maybe it's related to this issue It was involved in v0.3.0-alpha4 and has been fixed in v0.4.3-beta.1.

thanks, but I tried to upgrade dagger cue module to v0.4.3-beta.2, the problem still exist.

[TomChv]

Hey @lyzhang1999 It's been a long time you opened this issue!

Did you had the occasion to try our new dagger version and see if you still hit that issue?
You can onboard on our new version by following the documentation: https://docs.dagger.io/quickstart

Let me know if you have this problem again, if not I can close this issue 🚀

[helderco]

Closing since CUE is no longer supported.