Skip to content

rustc consumes > 50GB memory, completes eventually but def. stuck on something #129844

Open

Description

First of all, I am convinced it is more the fault of me doing something wrong. My hope and guess is that this is not a bug in rust, but just me misusing the language. I can however not find why it is happening, but I imagine it is something to do with an accidantal recursive trait bound or other generic related issue...

Of course it might be that already before aa4ea25cd2e4d624e8f82d1c48d375f285e3266b I was defining trait bounds or using generics in a "wrong" manner.

Logs attached for timings I was able to produce with nightly (in stable it was taking too long for me to be able to wait):

rustc.logs.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-typesystemArea: The type systemE-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleI-compilememIssue: Problems and improvements with respect to memory usage during compilation.I-compiletimeIssue: Problems and improvements with respect to compile times.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-typesRelevant to the types team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions