Open jamesrapadmi opened 3 weeks ago
You could try to create a repro where you take one test that you know is affected and parameterize it to run 2000 times?
We've managed to resolve the issue by using hardware acceleration within the stuff we're screenshotting. But I'm still not sure why
Do you mind providing a repro project? @jamesrapadmi Glad you fixed your issue but it would be helpful to see if the issue is related to paparazzi.
I can try to, but I'll likely struggle to find time to do that.
Description I have a project with a lot of screenshots (2000+). One series of the tests are now failing with an OOM. This is caused by
Canvas.getMatrix()
on theNopCanvas
returning an erroneous matrix ofMatrix{[8.6342721E14, 1.85162577E15, 1.9006225E20][-3.56884751E15, 1.66418037E15, 1.17585415E20][0.0, 0.0, 1.0]}
this then causes lottie to attempt to allocate a max size bitmap which causes the crash. (Issue occurs on this line)Steps to Reproduce Am struggling to reproduce this outside of my massive project, but it's something to do with reusing the canvas a lot (I can see that
mNativeCanvasWrapper
is the same across all the screenshots). The tests that are failing here pass if run by themselves, but not if I runn all the paparazzi tests.Expected behavior Screenshot should be generated, and test should not crash.
Additional information: