Patrick Neulichedl

Hi, we are facing this issue too, we were thinking about increasing our xmx from 4G to 6G. I've tried out `-Pdependency.analysis.check-binary-compat=false`, it seems to make matters a little better,...

@autonomousapps quick update I've now captured a few heap dumps, with and without binary compat enabled. I'm currently running them through MAT to see if I can spot something. If...

With my limited knowledge MAT doesn't really show anything obvious. One thing I noted is that there is always 1G of unreachable objects, which might be ok since they will...

Hi, I just had time to look at the dump without check binary compat enabled. This dump also shows 700MB for DefaultExternalModuleComponentGraphResolveState. I think that this is just the straw...

Quick update we have been running with v3.4.1 for almost 24hours without a repro. Since turning binary compat off doesn't seem to help a lot, I'd assume it's a change...

For me that is not the case :) See https://github.com/autonomousapps/dependency-analysis-gradle-plugin/issues/1604#issuecomment-3565839169 I reproduced it more than once with 3.5.0 with binary compat disabled. Also had a try with `-Ddependency.analysis.cache.max=0` because I...

Re-enabled cache disabled binary-compat again, just to make sure we still get an OOM.

Reproduced it in the first pipeline with `-Pdependency.analysis.check-binary-compat=false`