Token Refresh Min Memory #374
Replies: 4 comments
-
There is nothing related between version, free heap and token refreshment. The library use And when the token expired, all memory used by It is very critical memory usage in your case which only 13k is available for SSL related application to work. You should reduce the memory usage by avoid using global variables. |
Beta Was this translation helpful? Give feedback.
-
Thanks. In the same firmware here - I am using MQTT (pubsub library) with wificlientsecure client as well as firebase. I'm not sure i have the memory to run them both at the same time. I wonder if i have to disconnect the mqtt client when the token is being refreshed. |
Beta Was this translation helpful? Give feedback.
-
If you use You can set to lower value via For mqtt library, it ups on the SSL engine used. If it uses |
Beta Was this translation helpful? Give feedback.
-
Thank you for the advice! (this stretches well past the ESP Firebase library). |
Beta Was this translation helpful? Give feedback.
-
In upgrading from a previous version of the library - i now get a inconsistent crash when refreshing the firebase token. I have about 13/14k free memory and it looks like that's the issue (in a separate codebase to isolate the issue, it looks like i need about 17.5k in order to refresh the token successfully in the newest release). Previous releases were able to refresh with 13/14k memory i believe.
Are there any tips of tricks to reduce the mem needed for the token refresh process?
Beta Was this translation helpful? Give feedback.
All reactions