New firmware release, version 1.6.0.b1

[Neo]

@daniel Unfortunatelly the code is huge. I will try to reduce the area. I chekced also one auto tests only with LoRa initiation and Lora socket reading + gc.mem_free calls ... I saw that this test is hanging. I believe the real problem ties to memory leak /bad management. Here is the memory output at each second called soket recv and dump the mem_free:
Memory 19264
Memory 18656
Memory 18080
Memory 17504
Memory 16928
Memory 16352
Memory 15776
Memory 15200
Memory 14624
Memory 14048
Memory 13472
Memory 12896
Memory 12320
Memory 11744
Memory 11168
Memory 10592
Memory 10016
Memory 9440
Memory 8864
Memory 8288
Memory 7712
Memory 7136
Memory 6560
Memory 5984
Memory 5408
Memory 4832
Memory 4256
Memory 3680

[Neo]

@daniel Here it is your memory leak script:

def test2():

from network import LoRa
_lora = LoRa(mode=LoRa.LORA)

import socket
_socket = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
_socket.setblocking(False)    

import gc
gc.enable()   
while True:

    try:
        bytes = self._socket.recv(512)
        if len(bytes) > 0:
            print(" %s RECV %s" %  (self, bytes))
        
    except Exception as e:   
            print("_recv", str(e))    
            
    print('Memory %d' % (gc.mem_free()))

    utime.sleep(1)

test2()

[daniel]

@Neo, I modified your script in order to be able to run it:

from network import LoRa
import utime

class test:
    def __init__ (self):
        self._lora = LoRa(mode=LoRa.LORA)

        import socket
        self._socket = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
        self._socket.setblocking(False)    

    def run(self):
        import gc
        gc.enable()

        while True:
            try:
                bytes = self._socket.recv(512)
                if len(bytes) > 0:
                    print("%s RECV %s" %  (self, bytes))

            except Exception as e:
                print("_recv", str(e))

            print('Memory %d' % gc.mem_free())
            utime.sleep(1)

t = test()
t.run()

I get the following output:

Memory 54880
Memory 54320
Memory 53760
Memory 53200
Memory 52640
Memory 52080
Memory 51520
Memory 50960
Memory 50400
Memory 49840
Memory 49280
Memory 48720
Memory 48160
Memory 47600
Memory 47040
Memory 46480
Memory 45920

Which is totally correct, that's the way Python works. Memory is consumed as code runs, and when there's no more memory, the garbage collector kicks in and frees memory so that code can continue running. At some point you see:

Memory 5040
Memory 4480
Memory 3920
Memory 3360
Memory 2800
Memory 2240
Memory 1680
Memory 1120
Memory 560
Memory 0
Memory 54592
Memory 54032
Memory 53472
Memory 52912

However, if I add a gc.collect() line like this:

from network import LoRa
import utime

class test:
    def __init__ (self):
        self._lora = LoRa(mode=LoRa.LORA)

        import socket
        self._socket = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
        self._socket.setblocking(False)    

    def run(self):
        import gc
        gc.enable()

        while True:
            try:
                bytes = self._socket.recv(512)
                if len(bytes) > 0:
                    print("%s RECV %s" %  (self, bytes))

            except Exception as e:
                print("_recv", str(e))

            print('Memory %d' % gc.mem_free())
            utime.sleep(1)
            gc.collect()

t = test()
t.run()

I get:

Memory 55520
Memory 55664
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648
Memory 55648

Which at least in this test it shows that there's no memory leak...

[crankshaft]

@daniel - can you make a new announcement when a new beta is released, the topic of this current thread is ... version 1.6.0.b1 however I think it is now version 1.6.3.b1 ?

You have to trawl and check every post to see if a new release has been made and it's not very productive.

Or at least update the header

[livius]

@daniel said in New firmware release, version 1.6.0.b1:

bytes = self._socket.recv(512)

One hint if i can suggest something
what if you send something to this socket and this line recive some data?

bytes = self._socket.recv(512)

is this still the same result?
I can test it self only in the evening (and only on different socket - Wipy2) - but maybe result is different and you can find something interesting
If not then we can only wait for @Neo to provide some sample

@crankshaft good point

[Colateral]

@daniel It is strange that yesterday using this script the LoPy was hanging ... today I re powered and I didn't reproduce it anymore. It is true that yesterday I did a lot of operation before.

However the entire solution is still hanging and I need to understand why on 1.5.0 this is working and 1.6.x is not working.

[Neo]

@daniel It is still hanging. There is diff between your output and my output.... and I know why. My script is embedded in the app importing some additional modules.... that why mem is starting from 20K and not 50K as yours. Some of these modules have some static data and some of them have thread locks and Wifi data. Let me check.... the circle radius it will be reduced if I will take it one by one.

[Neo]

@Daniel I changed the LopY with new one + upgrade to 1.6.3b1 and I ran only your script. Now the output is the same as yours... .but it ALWAYS hanging after the mem displays 400. Here is the output:

Running
Soft resetting the LoPy
Memory 55280
Memory 54720
Memory 54160
Memory 53600
Memory 53040
Memory 52480
Memory 51920
Memory 51360
Memory 50800
Memory 50240
Memory 49680
Memory 49120
Memory 48560
Memory 48000
Memory 47440
Memory 46880
Memory 46320
Memory 45760
Memory 45200
Memory 44640
Memory 44080
Memory 43520
Memory 42960
Memory 42400
Memory 41840
Memory 41280
Memory 40720
Memory 40160
Memory 39600
Memory 39040
Memory 38480
Memory 37920
Memory 37360
Memory 36800
Memory 36240
Memory 35680
Memory 35120
Memory 34560
Memory 34000
Memory 33440
Memory 32880
Memory 32320
Memory 31760
Memory 31200
Memory 30640
Memory 30080
Memory 29520
Memory 28960
Memory 28400
Memory 27840
Memory 27280
Memory 26720
Memory 26160
Memory 25600
Memory 25040
Memory 24480
Memory 23920
Memory 23360
Memory 22800
Memory 22240
Memory 21680
Memory 21120
Memory 20560
Memory 20000
Memory 19440
Memory 18880
Memory 18320
Memory 17760
Memory 17200
Memory 16640
Memory 16080
Memory 15520
Memory 14960
Memory 14400
Memory 13840
Memory 13280
Memory 12720
Memory 12160
Memory 11600
Memory 11040
Memory 10480
Memory 9920
Memory 9360
Memory 8800
Memory 8240
Memory 7680
Memory 7120
Memory 6560
Memory 6000
Memory 5440
Memory 4880
Memory 4320
Memory 3760
Memory 3200
Memory 2640
Memory 2080
Memory 1520
Memory 960
Memory 400
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:

[Colateral]

@Neo On my LopY I have the same behavior. It is not necessary to iterate until end. Put gc.collect() after that sleep and .... that's it.

[madsdk]

I'm having big FTP stability problems after updating to this version. When I upload stuff it fails about half the time. Anyone else having problems with that? The problem is especially bad when uploading multiple files in one go.

[livius]

@daniel said in New firmware release, version 1.6.0.b1:

could it be that your file system is corrupted from previous firmware versions? Could you try:
import os
os.mkfs('/flash')

to format the file system and start from scratch...
Cheers,
Daniel

formated and tested on 1.6.1.b1 and still file corruption :(
now i am testing 1.6.3
on the left you have oryginal file - on the right corrupted

UPDATE
flashed to 1.6.3
formated and error is same -

but!

It is not visible at start see steps:

1. write e.g. test.py (copy normal onewire content twice to this file on computer)
2. copy this file to wipy throught ftp
3. download it and see if it is ok - yes it is ok
4. disable power (totally)
5. power on wipy
6. connect to it by ftp and download test.py - now it is corrupted

UPDATE2
It looks like it happened not always
after few try storing file and restart i finally have file ok (strange)

[PCA]

I confirm the issue with bluetooth callback disabled in 1.6.0.b1 is solved in 1.6.3.b2.
thanks @daniel

[Neo]

@Daniel On LoPy with 1.6.3.b2 the issue with the gc.collect()/memeory release is till persistent. Please run that test file with the LoRa socket recv and check it.

When do you think that we will have a fix for this? It is CRITICAL from many people point o view.

(sysname='LoPy', nodename='LoPy', release='1.6.3.b2', version='v1.8.6-464-g0f843911 on 2017-02-17', machine='LoPy with ESP32', lorawan='1.0.0')

[daniel]

@Neo I agree it's super CRITICAL. It's on the top of our priorities at this moment. We'll do our best to resolve it ASAP.

Cheers,
Daniel

[JF002]

@Neo said in New firmware release, version 1.6.0.b1:

@Daniel On LoPy with 1.6.3.b2 the issue with the gc.collect()/memeory release is till persistent. Please run that test file with the LoRa socket recv and check it.

When do you think that we will have a fix for this? It is CRITICAL from many people point o view.

(sysname='LoPy', nodename='LoPy', release='1.6.3.b2', version='v1.8.6-464-g0f843911 on 2017-02-17', machine='LoPy with ESP32', lorawan='1.0.0')

I also still have this bug... I was hoping it would be resolved in this update (1.3.6), but it doesn't seem to be the case... Do you want us to fill a bug on github?

Thanks!

[daniel]

@JF002 yes please do report it on Github with a piece of code to reproduce the issue easily (include your boot.py as well if possible). Thanks!

[JF002]

@daniel said in New firmware release, version 1.6.0.b1:

@JF002 yes please do report it on Github with a piece of code to reproduce the issue easily (include your boot.py as well if possible). Thanks!

Here it is :) https://github.com/pycom/pycom-micropython/issues/82

[crankshaft]

@daniel - as you requested, I re-posted my issues / bugs on github duplicating the posts I already made on the this forum, and surprise, surprise, no replies on the github issues either.

I am very disappointed that despite posting my issues, nobody has taken a few minutes to verify / validate or even ask me any questions regarding these issues, I think that you really need to review your priorities.

I have spent the last week porting my code to ESP8266 and I face none of the issues that I posted on this forum regarding guru mediation crashes, intermittent loss of socket connections etc etc etc.

Remember that it takes a long time to develop a good reputation, and very little time to loose it !

:-(

[daniel]

@crankshaft we have seen your issues and we are working on fixing them, but it takes time, the ESP-IDF is in an unstable state which doesn't make things easy.

[crankshaft]

@daniel - someone needs to reply to each issue posted by users, we are not mind readers !