-
Notifications
You must be signed in to change notification settings - Fork 2k
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
fix potential memory leak in WiFiManagerParameter::setValue #1206
Conversation
So this would address a memory leak when calling setValue multiple times with changing values, correct? |
I think so |
I need reviewers lol, ill try to look at this when i get a chance |
reverted, crashes esp32 bad array access assertion "heap != NULL && "free() target pointer is outside heap areas" |
@cpainchaud I had to revert this it was crashing esp32 |
I saw that, it's weird actually, it means that another part of the code is relying on that memory to never be freed while it's obviously leaked .... |
yeah I did not really look at it at all, was busy on stuff. it crashed immediately also which is odd.. |
This is because _value is not initialized in the constructor, or rather the Simply do |
I think this is right, please check |
Works fine, doesn't crash |
Or maybe it does? Just re-tested this. Initial flash goes fine, but if I OTA update "my" application again, I get a |
I think this is because |
Thanks for testing this, let me know what you find or if you do not, etc That error could also be a partition size issue or ota size issue |
on ESP8266, this |
Thanks, I havent had time to really look at this, and I am pretty sure I left a mix of null and nullptr in here, It need to be reworked to be memory safe, and I was just trying to figure out how make this safer when these are out of scope ( which alot of people do ) and make it not crash |
No description provided.