Testing #647

Code review imlightsw to look for leaks

Added by Hammel 12 months ago. Updated 11 months ago.

Status:NewStart date:18 Jul 2018
Priority:UrgentDue date:
Assignee:Hammel% Done:


Target version:Iron Man - 002 - MVP
Severity:01 - Critical


Many of the libraries being used should be safe, but they should be reviewed. All allocations should be static, as described in this StackOverflow discussion.

Also, all static strings (like path names for SPIFFS) should be wrapped in F() to push them to PROGMEM as discussed in this StackExchange thread.


#1 Updated by Hammel 11 months ago

And remove as many stack variables as possible to speed operation in exchange for program size. There are plenty of variables I could reuse (simple int's for example).

Also available in: Atom PDF