On 08/22/2017 10:47 AM, Thiago Macieira wrote: > On Tuesday, 22 August 2017 09:36:19 PDT Thiago Macieira wrote: >> This is not an IoTivity problem. Your device is out of memory. > > It could be an IoTivity problem if it's leaking memory.
Is logging on so you can see more of what is failing? Opportunity to stick in an oar here: at the moment, a static checker run (Coverity) reports 235 possible memory leak locations including Java jni code, but my general impression without having examined every one in detail is that they're mostly not in mainstream cases: very many are failure to fully clean up in error cases, causing something to leak as it goes out of scope due to error exit (but usually, we were already in memory trouble at that point); unit tests, which are one-shot rather than something crucial like stack code, etc. Not to say they're unimportant, but the ones I've scanned don't look like they're evidence of persistent memory leaks in the stack. I believe the contractor working on quality issues is looking at static checker fails, so I'm not spending my cycles looking too hard at these, there are only so many cycles to go around. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
