Luasocket with EEP? (solved)

!!! Please ensure, that your contribution or question is placed into the relevant section !!!
Questions about rolling stock, for example, do not belong in "Questions about the Forum". Following is perhaps the right area where your question will be better looked after:
General questions to EEP , Splines, rolling stock, Structures in EEP, landscape elements, Signalling system and controlling, designers, Europe-wide EEP meetings , Gossip
Your cooperation to keep the forum clear is appreciated.
  • Good news / bad news


    Good news: Using Benny's socket/core.dll and Copas (plus some more libraries to use sha1 and web socket frames) I was successful to establish full duplex web socket communication between EEP and a javascript client in the browser:




    Bad news: EEP crashes after short time in different ways: Sometimes

    - EEP just vanishes

    - EEP shows a message and vanishes

    - EEP shows a message and keeps running but looses Lua and shows no log messages any more





    If anybody likes to experiment with my Lua programs, just request them via PN (as long as the crash is not solved I hesitate to publish it on GitHub).


    Kind regards

    Frank

    EEP 6 in 2011, EEP 13 ab Januar 2019, EEP 15 ab Mai 2019 (wegen dem umfangreicheren Lua-Befehlssatz)

  • Hi Frank,


    your error reports raise the suspect in my mind, that you experience a memory leak. If that's true, you should see a constantly growing memory consuption while your web sockets are communicating with each other. Perhaps, Benny (BH2) might also have a look on this.


    Cheers

    Christopher

    PC: Intel i7-7700K; 64bit; 4,2 GHz; 16GB RAM; GeForce GTX 1080 (8 GB); Win 10; EEP 6, 13.2 Plugins 1+2, 14.1 (Dev), 15 (Dev); HomeNOS 14 (Dev)
    Laptop: Intel i5 3230M; 64bit; 2,6 GHz; 8GB RAM; GeForce GT740M (1 GB); Win 8.1; EEP 6, 13.2 Plugins 1+2; HomeNOS 13 (User)

  • Hi Christopher,


    I guess it's not about memory as it stays stable at ~360 MB in the process explorer.


    While checking memory consumption in the process explorer I got an early crash (no message, but EEP just vanishes) even before starting the web socket client.


    Than means that the crash already could happen right after loading socket/core.dll and calling socket.bind().


    Frank

    EEP 6 in 2011, EEP 13 ab Januar 2019, EEP 15 ab Mai 2019 (wegen dem umfangreicheren Lua-Befehlssatz)

  • Thanks for the clarification.

    But that means probably, that either socket/core.dll is not compiled correctly or incompatibel with EEP16. Bad luck! :az_1:


    Christopher

    PC: Intel i7-7700K; 64bit; 4,2 GHz; 16GB RAM; GeForce GTX 1080 (8 GB); Win 10; EEP 6, 13.2 Plugins 1+2, 14.1 (Dev), 15 (Dev); HomeNOS 14 (Dev)
    Laptop: Intel i5 3230M; 64bit; 2,6 GHz; 8GB RAM; GeForce GT740M (1 GB); Win 8.1; EEP 6, 13.2 Plugins 1+2; HomeNOS 13 (User)