[GH-ISSUE #660] Compilation ran my VM out of memory #238

New issue

Closed

opened 2026-02-27 08:16:05 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 08:16:05 +03:00

Owner

Originally created by @wjk on GitHub (Aug 30, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/660

I set to compile lldap from source, following the instructions in the README. It compiled all the dependent modules, but hung when it got to the lldap binary itself. I noticed that at one point during the build, the system UI was not responsive to my inputs. I left it to sit for a while and came back to see that the compiler process was killed (as in an actual SIGKILL). Given the symptoms, it is likely that the kernel’s OOM killer did this. Does anyone have any hints as to what might be going wrong?

Environment:

M1 MacBook Air (arm64 processor)
Virtualization program: UTM version 4.3.5
OS: Debian 11 “Bullseye”
Reported memory: 3.8GB
Rust compiler version: 1.72.0

Originally created by @wjk on GitHub (Aug 30, 2023). Original GitHub issue: https://github.com/lldap/lldap/issues/660 I set to compile lldap from source, following the instructions in the README. It compiled all the dependent modules, but hung when it got to the lldap binary itself. I noticed that at one point during the build, the system UI was not responsive to my inputs. I left it to sit for a while and came back to see that the compiler process was killed (as in an actual SIGKILL). Given the symptoms, it is likely that the kernel’s OOM killer did this. Does anyone have any hints as to what might be going wrong? Environment: * M1 MacBook Air (arm64 processor) * Virtualization program: [UTM](https://getutm.app/) version 4.3.5 * OS: Debian 11 “Bullseye” * Reported memory: 3.8GB * Rust compiler version: 1.72.0

kerem

2026-02-27 08:16:05 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-27 08:16:05 +03:00

Author

Owner

@nitnelave commented on GitHub (Aug 30, 2023):

I don't know exactly, but LLDAP uses quite a few convenience crates that generate code, and those proc macros can be heavy on the compiler. I'd blame rustc and tell you to get a bigger VM :D

@nitnelave commented on GitHub (Aug 30, 2023): I don't know exactly, but LLDAP uses quite a few convenience crates that generate code, and those proc macros can be heavy on the compiler. I'd blame rustc and tell you to get a bigger VM :D

kerem commented

2026-02-27 08:16:05 +03:00

Author

Owner

@Masgalor commented on GitHub (Aug 31, 2023):

If you want to build LLDAP for Debian_11 your vm will need at least 4GB of memory and 10GB of disk space (without swap).
Source

@Masgalor commented on GitHub (Aug 31, 2023): If you want to build LLDAP for Debian_11 your vm will need at least 4GB of memory and 10GB of disk space (without swap). [Source](https://build.opensuse.org/package/statistics/home:Masgalor:LLDAP/lldap/Debian_11/x86_64)