Neil P.

@peterjc do you have a link available? I found [this thread](https://discuss.python.org/t/the-difference-between-python-setup-py-build-ext-i-and-pip-install-e/3716/11) where it's mentioned that `build_ext -i` isn't available through pip yet. Not sure if anything has changed since then...

I can give that a shot and see if it allows the tests to resolve the compiled modules correctly

@peterjc Local tests are working with the `pip install -e .` command. It creates the `*.so` libraries in place in the source tree. Updated the instructions accordingly.

Any update on this @peterjc / @mdehoon / @JoaoRodrigues ?

My opinion is to just merge this as is since it will get the instructions working. If someone has a better approach than the instructions can be updated again in...

@jwnasambu @dkayiwa Updated to remove all formatting changes

Looks like this issue still exists with [Material PullRefresh](https://developer.android.com/reference/kotlin/androidx/compose/material/pullrefresh/package-summary) now that `SwipeRefresh` is deprecated.

I have created a reproduction using the latest release (`4.11.1`), it can be found [here](https://github.com/npars/RobolectricSdkPerf). You can run with `./gradlew test` and a heap file will be generated in `./app`...

Realized I could write a failing integration test within robolectric so here you are: https://github.com/robolectric/robolectric/compare/master...npars:robolectric:constrained-memory-test With a bigger project like Robolectric we see it fail with a xmx of 512mb:...

I do Android development in my day job, I can probably take a look in the near future