Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I solve outbox: outbox_enqueue(53): Memory exhausted issue ? (IDFGH-14481) #15251

Open
Vaibhav0216 opened this issue Jan 22, 2025 · 1 comment
Labels
Status: Opened Issue is new

Comments

@Vaibhav0216
Copy link

I am storing large data in the sd card sending this data through the mqtt to cloud. But I am facing the below issue.

I (85763) example: Available heap before allocation: 7880
I (85763) example: After allocation, Free Heap: 5572
I (85773) TAG: Processing file: /sdcard/data_tel_1737459639000.json, Size: 2285, Heap: 5572
File Size : 4116 bytes
E (85983) outbox: outbox_enqueue(53): Memory exhausted
I (85993) MQTT: Outbox size: 80006
E (85993) MQTT: Failed to enqueue telemetry data: -1
I (86003) example: After freeing, Free Heap: 7880

At starting heap size is very large almost 90k I am clearing the object string allocated by malloc ( dynamically ) how can I control on heap size increasing ?

How can I resolve this error?

@espressif-bot espressif-bot added the Status: Opened Issue is new label Jan 22, 2025
@github-actions github-actions bot changed the title How do I solve outbox: outbox_enqueue(53): Memory exhausted issue ? How do I solve outbox: outbox_enqueue(53): Memory exhausted issue ? (IDFGH-14481) Jan 22, 2025
@euripedesrocha
Copy link
Collaborator

@Vaibhav0216 the issue here is that you don't have enough memory to proceed with publishing the message.

The solution will depend on your system, I'm considering that you don't intend to switch to a module with external RAM.
Given the size of messages your system at some point might always reach this scenario. These are my suggestions:

In summary, the solution is to control the message publishing process more closely and retry it when the memory is available.

I can give you more suggestions if you provide more information about your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

3 participants