Page 1 of 1

Take care with upgrading Mono to 6.10

Posted: Sat 29 Aug 2020 11:27 am
by HansR
Please note that there may be a problem with a RPi system upgrade of Linux and Mono (same time) to versions 5.4.51-v7+ armv7l and respectively. See the console stackdump of Mono during a CumulusUtils run. Yesterday I had a report from @billy which was exactly the same as I had today while running CumulusUtils. I thought then it might have been a hardware error or a SD card error but apparently it is something structural.

My versions are:
Raspbian Buster / 5.4.51-v7+ armv7l (before: 4.19.118)
Mono JIT compiler version (before:
I am unaware of any software issue, but the origin most likely is in Mono (what the message says) - note that @Billy had not upgraded Linux at that time - or in Visual Studio C# which of course cooperates with the runtime. CumulusUtils seems to be running fine and until now the modules and/or website are generated correctly as far as I can see.
I assume there is no issue on Windows (native .NET).

I will not generate new releases until I know more about this stackdump of Mono and its effects.
I have no idea of its effects on CMX itself.
    Aantekening 2020-08-29 130050.png

    Re: Take care with upgrading Mono to 6.10

    Posted: Thu 03 Sep 2020 7:32 pm
    by mcrossley
    I'm running with MX for a while and so far haven't seen an issue (Buster 5.4.51-v7l+)

    Re: Take care with upgrading Mono to 6.10

    Posted: Thu 03 Sep 2020 7:51 pm
    by HansR
    Interesting. So far I have only had a report from billy and myself.
    Weird but seems some kind of false alarm so far.

    Re: Take care with upgrading Mono to 6.10

    Posted: Fri 04 Sep 2020 3:05 am
    by billy
    Hi Hans, re your comment in the announcement for the latest release
    NOTE: I continued work on research of this Mono Error. So far no result. I appreciate any observation report. If it occurs on your system you will find files with a name like mono_crash.0.0.json in your cumulus directory.
    I hadn't noticed the mono_crash.0.0.json file until you pointed out its existence. Attached is the one produced by my latest daily update run - which seems to have resulted in everything working as per normal, including the map (which is nonetheless still a bit fickle - sometimes still doesn't work). I don't usually run cutils outside of a daily crontab. I'll try and be more observant in future :)