Hey,
I found that one building the door at the Artifactory.
Are you using files as function arguments?
The default arduino sd card library has issues with memory leaks in odd circumstances. I found that when you pass a file handle as an argument, it calls new() again and you can never fully free the memory.
Then the stack collides with the heap and you get undocumented results.
It might be worth skim reading the source for that lib, there really was quite a bit of weirdness in the memory management that dictates how it should be used.
(Oh, and the default example leaks like a sieve)
Cheers,
Brett
--
You received this message because you are subscribed to the Google Groups "Connected Community HackerSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to connected-community-h...@googlegroups.com.
To post to this group, send email to connected-commu...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/connected-community-hackerspace/BLU180-W46B4799721B48188A76ED1B8700%40phx.gbl.
For more options, visit https://groups.google.com/d/optout.
I've not found a better library.
The memory leak only occurs in very specific uses, so the workaround is not hard.
If you skim read the library, you'll find the constraints and it's smooth sailing from there.
iirc, it takes only a thousand or so lost file handles to blow the stack and crash the main loop, so testing for leaks is pretty easy: Cycle the open/close code and print a counter to serial until it crashes or reaches 10k.
Regards
Brett
To view this discussion on the web, visit https://groups.google.com/d/msgid/connected-community-hackerspace/BLU180-W748C01012CE81454768187B8700%40phx.gbl.
To view this discussion on the web, visit https://groups.google.com/d/msgid/connected-community-hackerspace/BLU180-W23A22BD6B8D85725223F0EB8700%40phx.gbl.