You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering an issue on an embedded device that publishes images at a fixed FPS. In my code, after creating a message, I noticed that using to_bytes_packed() causes the memory consumption to steadily increase until the device eventually runs out of memory, requiring a restart. Interestingly, this does not happen when using to_bytes().
I am wondering if there’s anything specific about the packed serialization that could explain this behavior.
Hi, thank you for your great work on pycapnp!
I am encountering an issue on an embedded device that publishes images at a fixed FPS. In my code, after creating a message, I noticed that using
to_bytes_packed()
causes the memory consumption to steadily increase until the device eventually runs out of memory, requiring a restart. Interestingly, this does not happen when usingto_bytes()
.I am wondering if there’s anything specific about the packed serialization that could explain this behavior.
Here is a quick example to reproduce the issue:
Python:
3.11.11
pycapnp:
2.0.0
schema
byte_image.capnp
test.py
Logs:
100 runs
150
runs:200
runs:For
to_bytes()
,Mem usage
stays roughly the same; however, forto_bytes_packed()
, it keeps increasing.The text was updated successfully, but these errors were encountered: