wifi.ping() memory leak and undefined #6051
Replies: 1 comment
-
Posted at 2018-08-01 by DrAzzy The "undefined" looks normal, as you're printing to the console the result of wifi.ping() which doesn't return anything. The memory hemorrhage, though... 85 jsvars per iteration! Posted at 2018-08-02 by @gfwilliams Ok, I just made a change which will hopefully fix it (looks like the ping responses were causing leaks) - so hopefully cutting edge builds will have this fixed. Posted at 2018-08-02 by @MaBecker @gfwilliams, thanks for checking and fixing it ! Posted at 2018-08-02 by @MaBecker can confirm that fix is working as expected test snippet:
output:
Posted at 2018-09-24 by parker Problem with memory leak in wifi.ping() still exist. espruino_1v99_esp8266 Where I can get fixed version?
Posted at 2018-09-27 by @MaBecker You have to download the Travis build to get this fix Posted at 2018-09-27 by parker What is the Travis build? Where I can get it? Posted at 2018-09-27 by parker I have found Travis build, thank you! Posted at 2018-09-27 by @MaBecker 👍🏻 Posted at 2018-09-27 by @MaBecker Check this file for all latest changes Posted at 2018-09-27 by parker Thank you, MaBe! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2018-07-31 by Denis
Hello.
I use wifi.ping wifi.ping with setInterval under v1.96 and NodeMCU, it have memory leak in case if I use callback function and function wifi.ping always return undefined. See code and result below.
How it's may be solve? I need to have result of ping: successful or fail, without check of callback argument, in this case memory leak will not present.
result:
Beta Was this translation helpful? Give feedback.
All reactions