Interesting memory usage behavior we've been seeing in

graphql-kotlin

1.3.0 vs 1.2.1: When running our unit tests on CircleCI, we're hitting the 4G max memory usage for a container limit. We can get around it by setting

JAVA_TOOL_OPTIONS=-XX:MaxRAM=1g

, but somewhat concerned that this is newly needed? Has anyone else seen anything similar?

Did not notice it myself - there weren't many changes between the versions, mostly just update from reflections to ClassGraph lib. By any chance could you share some sample project that exhibits this behavior?

https://github.com/trib3/leakycauldron/pull/189 is the dependabot PR, I think you should be able to see the prior failed builds for that branch in circleci as well

unfortunately those build logs don't tell much 😞

yeah, just that 137 means the container used > 4G memory and processes got killed

when running it locally i do see higher memory usage by

ClassGraph

vs

Reflections

libs

hmm, that would make sense to me, but replacing all our tests

SchemaGeneratorConfig(listOf())

with

SchemaGeneratorConfig(listOf("java.lang"))

is still showing the error without a more restricted java memory usage setting; is that not a good way to narrow the scope or do we just need to tweak the mem usage settings better for the restricted CI environment?

instead of

java.lang

you should be pointing to

com.trib3.graphql

or something like that

yeah we are running tests in parallel. looks like pointing to

com.trib3.graphql.subpackage

does pass without tweaking the memory settings fwiw