1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • 1.12 A39 Linux/64 Compiled 2018/04/01 17:21:30

    From bcw142@21:1/145 to g00r00 on Monday, April 02, 2018 13:38:25
    On the last issues I was having my telnet server was set as IPV4+IPV6, but I had problems getting something repeatable on that. At any rate that's now an old Alpha so I updated yesterday to:
    v1.12 A39 Linux/64 Compiled 2018/04/01 17:21:30
    Now I'm seeing the issues Fat Rastus mentioned under:
    Bug Report: v1.12 A39 Linux/64 Compiled (2018/04/01)

    I've been having what I think is the same issue or related with nodespy.
    If I open nodespy and go to localhost, I can login and things are fine,
    till I try to logout. Then it just hangs on the last screen. I end up
    with a hung nodespy:
    3716 pts/0 Ss+ 0:00 bash
    3761 pts/5 Ss+ 0:00 bash
    6381 pts/9 Ss 0:00 -bash
    6665 pts/9 RL+ 0:32 ./nodespy
    6667 pts/9 Z+ 0:00 [nodespy] <defunct>
    6749 pts/13 Ss 0:00 -bash
    6796 pts/13 R+ 0:00 ps a

    If I kill it, the mis takes 100% of CPU and I can do little or nothing
    with the system (after an hour I got the PID for mis killed). I did this
    twice so far, so it seems repeatable. If I don't try to kill the nodespy
    I think things run OK, I think. Did see:
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    34 root 20 0 0 0 0 R 99.7 0.0 41:49.68 kswapd0
    7074 bcw 20 0 8644224 3.205g 1068 S 0.3 85.4 17:12.39 mis

    So, there's a memory leak (85.4% of memory used by mis). That's likely what's taking all my CPU time after a while. It is my AlphaTest system so not such
    an issue if it goes down. I plan to try waiting a long time for the hung nodespy, I might not be waiting and thus causing the memory issue with the
    kill command.

    --- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From g00r00@21:1/108 to bcw142 on Monday, April 02, 2018 17:09:03
    Now I'm seeing the issues Fat Rastus mentioned under:
    Bug Report: v1.12 A39 Linux/64 Compiled (2018/04/01)

    Yes that is true with NodeSpy. I fixed that as well I just haven't made the April 2nd build yet. I plan to do that shortly so keep an eye out today for another pre-alpha where Nodespy should hopefully be fixed up.

    Thanks for the report!

    --- Mystic BBS v1.12 A39 2018/04/01 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)