Memory leak, missing a few bytes #225
Replies: 7 comments
-
Posted at 2014-03-11 by DrAzzy Those are not bytes - those are memory blocks, 20 bytes each. Does trace() show the cause of the missing memory? That's what Gordon suggested I use to investigate my own memory leak issue. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2014-03-11 by @gfwilliams @sacha - thanks! I'll get on to this - it looks like an issue with debounce. It should also pay attention to |
Beta Was this translation helpful? Give feedback.
-
Posted at 2014-03-11 by Sacha Hi Gordon, Thanks. Had the same memleak befor using repear: true. Regards Sacha |
Beta Was this translation helpful? Give feedback.
-
Posted at 2014-03-11 by @gfwilliams If you remove |
Beta Was this translation helpful? Give feedback.
-
Posted at 2014-03-11 by Sacha Hi Gordon, I can confirme this. Without debounce there is no mem leak. Sacha |
Beta Was this translation helpful? Give feedback.
-
Posted at 2014-03-11 by @gfwilliams Should be fixed when 1v56 comes out - or on the 'latest' builds |
Beta Was this translation helpful? Give feedback.
-
Posted at 2014-03-11 by Sacha Thanks Gordon. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2014-03-10 by Sacha
Hello Gordon,
Received the Espruino. What i nice device! But i think i've found a mem leak.
Using 1v55.
The simple code:
// Callback function for din change
After uploading process.memory(); shows 1766 free.
Each buttonpress decreases the free mem by aprox. 2 bytes.
Regards
Sacha
Beta Was this translation helpful? Give feedback.
All reactions