Since > 38.40.1 renovate exits with status code 134

[otbe]

What would you like help with?

I think I found a bug

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Gitlab

Please tell us more about your question or problem

Somewhen after 38.40.1 a lot of renovate runs across different projects start to fail with Command failed with exit code 134

I tested versions: 38.43.0 and 38.44.3

Its a run of a single repository with a moderate amount of dependencies (<50).

The annotation marks when something > 38.40.1 was deployed.

That means from ~10% memory usage (of 4GB), it went up to >50% after the deployment which also explains why the process is killed at some point.

Logs (if relevant)

The last log line before this happens is:

Logs

Starting package releases lookups

Theres no error/exception apart from renovate just exciting.

[rarkins]

Try googling that error

[otbe]

I know what it is but why does it start after 38.40.1? :)
Read the changelogs and couldnt pin it down to a specific change. Is renovate just needing more mem than usual? No leak or regression?

[HonkingGoose]

Please update to Renovate 38.46.1 (or newer). And let us know if updating fixed the problem, or not.

Context

This discussion says 38.40.1 causes Renovate to use a lot more memory than before:

• Multiple customManagers for the same file cause geometric growth in dependency count, leading to memory exhaustion #30906

We reverted to the old situation with this PR (released in 38.46.1):

• fix: Revert "refactor: Flatten update lookup tasks" #30933

[github-actions[bot]]

Hi there,

You're reporting a problem with an old version of Renovate. Please try the latest version and tell us if that fixes your problem.

Be sure to provide updated logs once you have run with a newer version.

Good luck,

The Renovate team