Vangelis Stable, shutdown/reboot no longer works depending on snapshot

Software
1

I’m installing Vangelis Stable on my 5.1 kit.

Until now everything worked as expected.
But after changing some settings in Webconf Hardware Wiring Zynthian no longer shuts down properly but restarts on an error 134.

When stopping Zynthian service the following message appears in the log, apparently there is a corrupted pointer somewhere.

Oct 25 08:36:40 zynthian systemd[1]: Stopping zynthian.service - Zynthian User Interface...
Oct 25 08:36:41 zynthian startx[2045]: ====================== ZYNSEQ MIMALLOC STATS ====================
Oct 25 08:36:41 zynthian startx[2045]: heap stats:     peak       total       freed     current        unit       count
Oct 25 08:36:41 zynthian startx[2045]:   reserved:     1.0 GiB     1.0 GiB    64.2 KiB     1.0 GiB
Oct 25 08:36:41 zynthian startx[2045]:  committed:     3.4 MiB     3.6 MiB     2.0 MiB     1.6 MiB
Oct 25 08:36:41 zynthian startx[2045]:      reset:     0
Oct 25 08:36:41 zynthian startx[2045]:     purged:     1.9 MiB
Oct 25 08:36:41 zynthian startx[2045]:    touched:     0           0           0           0                                ok
Oct 25 08:36:41 zynthian startx[2045]:      pages:   745         745           0         745
Oct 25 08:36:41 zynthian startx[2045]: -abandoned:     9         287         278           9                                not all freed
Oct 25 08:36:41 zynthian startx[2045]:  -reclaima:     5
Oct 25 08:36:41 zynthian startx[2045]:  -reclaimf:     0
Oct 25 08:36:41 zynthian startx[2045]: -reabandon:     0
Oct 25 08:36:41 zynthian startx[2045]:     -waits:     0
Oct 25 08:36:41 zynthian startx[2045]:  -extended:     0
Oct 25 08:36:41 zynthian startx[2045]:  -noretire:     0
Oct 25 08:36:41 zynthian startx[2045]:     arenas:     1
Oct 25 08:36:41 zynthian startx[2045]:    -purges:     4
Oct 25 08:36:41 zynthian startx[2045]: mmap calls:     2
Oct 25 08:36:41 zynthian startx[2045]:    -commit:     0
Oct 25 08:36:41 zynthian startx[2045]:     -reset:     0
Oct 25 08:36:41 zynthian startx[2045]:     -purge:    17
Oct 25 08:36:41 zynthian startx[2045]:    guarded:     0
Oct 25 08:36:41 zynthian startx[2045]:    threads:     1           2           2           0                                ok
Oct 25 08:36:41 zynthian startx[2045]:   searches:     0.0 avg
Oct 25 08:36:41 zynthian startx[2045]: numa nodes:     8
Oct 25 08:36:41 zynthian startx[2045]:    elapsed:   796.877 s
Oct 25 08:36:41 zynthian startx[2045]:    process: user: 68.167 s, system: 51.363 s, faults: 0, rss: 250.0 MiB, commit: 3.4 MiB
Oct 25 08:36:44 zynthian startx[2045]: zynmixer_bus mixbuses ended
Oct 25 08:36:44 zynthian startx[2045]: free(): invalid pointer
Oct 25 08:36:44 zynthian startx[1250]: ./zynthian.sh: line 381:  2045 Aborted                 ./zynthian_main.py
Oct 25 08:36:44 zynthian startx[1250]: *******************
Oct 25 08:36:44 zynthian startx[1250]: EXIT STATUS => 134
Oct 25 08:36:44 zynthian startx[1250]: *******************

I guess this has something to do with this issue.

In the past I had a comparable problem that was fixed by running a Webconf Update again (even if there were no updates) but that no longer works.

I already went back to the original Customization Profile but that does not work either.

Any help would be greatly appreciated. I don’t want to re-flash the SD card as that would take more than 3 hours to configure everything. Plus when I am finished it starts all over…

Regards,
Hans.

Edit: UI log is here:
UIlog.zip (1.6 KB)

2

It looks like this is not only caused by a wiring change, but is dependent on the snapshot that is loaded.
For some snapshots the shutdown/reboot is performed normal, for others it is not and runs in an invalid pointer error 134.

These two prevent normal shutdown:
Snapshots.zip (11.7 KB)

This problem occurs only on my official V5.1 Kit. On the V5 clone everything works normal.

image
image625×278 6.28 KB

3

I thought the problem was solved when I removed the .backup directory and last_state.zss, but the problem has returned.

It’s a pity the only message was invalid pointer because that is almost impossible to trace.

4

Got the same issue on a beta to stable update. After using a fresh image, the issue is no longer present.
Reported also here: ZynthianOS Vangelis Stable 2610 is released - #15 by travelrec

5

For me it’s the opposite. The update from beta to stable works fine, the fresh image has the problem.

Now both have the same problem :sob:.

There is some weird bug that reacts to snapshots (and is perhaps(?) triggered by wiring changes).

I think I’ll go back to Oram for the time being.

6

Then, I think, it is triggered by any internal chain, FX, whatever setting and the image itself doesn’t matter whether it’s a fresh or updated one.