Closed thiagopromano closed 1 month ago
Please let us know if you have better results either in 0.8 or 0.9.
We were able to stop receiving this error by decreasing our application's peak memory usage. It's likely that the error was caused by something important being evicted during periods of high memory usage.
In our situation, we achieved this by rewriting a costly algorithm into a NIF written in Rust with several optimizations, such as using sparse matrices.
If anyone encounters this issue, I suggest checking the memory usage of your application.
Hey,
We have been getting this error sometimes when calling a
Defn
in production, retrying immediately always solves the problem.We are currently running
exla 0.7.3
on thehost
platform. We have not yet updated to0.8.0
as we depend on Bumblebee which doesn't support it yet.I could not reproduce it locally as it happens randomly, retrying always works. We obtained this error 37 times out of (estimated) ~100k executions.
The same error also presents itself with the symbols
main.29
andmain.5
.Here is the stack trace: