frigate: enabling frigate module causes *excessive* eval RAM usage (and OOMs)

[colemickens]

Describe the bug

A clear and concise description of what the bug is.

Steps To Reproduce

I apply this diff to one of my NixOS hosts (an aarch64-multiplatform being cross-compiled on x86_64-linux), then try to eval it:

{
  config = {
    # ...
    services.frigate.enable = true;
    services.frigate.hostname = "frigate.mickens.us";
    # ...
  };
}

But it eats up ~18GB+ of RAM (hard to say with zram, etc), and eventually OOMs.

This is on top of: 1355a0cb (current nixos-unstable)

Not sure if there's some other nginx setup that's needed, but if so, there should probably be some asserts or something. Anyway, this is quite odd. Can't say I've ever seen anything quite like this.

cc: @mweinelt

---

Add a 👍 reaction to issues you find important.

[mweinelt]

Likely a duplicate of #338231, which affects cross python.

[colemickens]

Wow thanks @mweinelt ! Closing and tracking that.