"The memory is the first thing to go."(I don't remember who told me that)
The most obvious sign of a memory problem is when the compiler tells you that your sketch is too big.
But many memory problems show much more subtle symptoms. Your program may load, but not run. It may crash hard, or just start acting funky.
Last updated on 2015-02-27 at 03.10.05 PM
Published on 2013-08-02 at 02.19.49 PM
If your program compiles and loads successfully, but any of the following statements are true, there is a good chance that you have a memory problem.
"My program worked fine until I" (choose one)
- "Included one more library"
- "Added some more LED pixels"
- "Opened a file on the SD card"
- "Initialized a graphical display"
- "Merged in another sketch"
- "Added a new function"
If you think you might have a memory problem, you can skip right to the "Solving Memory Problems" page. But you should first take a look through the next few pages to better understand Arduino memory and how it works.