Repeated rendering to Canvas crashes app on iOS #115
Comments
@SomaKishimoto, thanks for reporting this issue. Can you share the canvas drawing source code? If the canvas context is used in a rendering loop, then my hunch is that it is missing the |
@raedle , thanks for your prompt reply. we refer to this example and do continuous rendering with |
@SomaKishimoto, there is an issue with the recent change to the iOS canvas. We are investigating on a forward fix. In the meantime, the The following PlayTorch Snack shows the usage for |
@raedle , thanks! We'll try it and let you know if there is any progress! |
Works fine, @raedle! Thanks a lot. |
Thanks for reporting back. Closing task! |
@raedle , Unfortunately, repeated rendering crashes app on iPad Air Gen3 (OS15.5) after running for 4 hours. I confirmed that the app was working for at least 9 hours on iPhone. |
@SomaKishimoto, thanks for reporting the memory warning. Can you provide more info on the following three questions?
const isHermes = () => !!global.HermesInternal; https://reactnative.dev/docs/hermes#confirming-hermes-is-in-use
|
@raedle , thanks for your prompt reply.
It's me that brought this question up, but this problem may be caused by something else. |
Thanks @SomaKishimoto, and please let us know if the issue is with PlayTorch! |
Version
0.2.1
Problem Area
react-native-pytorch-core (core package)
Steps to Reproduce
Error message:
Message from debugger: Terminated due to memory issue
just before the crush:
W0821 11:40:23.873222 1881387008 JSIExecutor.cpp:381] Memory warning (pressure level: 1) received by JS VM, unrecognized pressure level
The crush doesn't occur when this commit is ignored.
v0.2.0 doesn't crush app.
What kind of measures should I take?
Expected Results
No response
Code example, screenshot, or link to repository
No response
The text was updated successfully, but these errors were encountered: