makew0rld/amfora

Crash on ARM64 (RaspberryPi CM4, Alpine Linux 6.1.64)

Carlo-Monte opened this issue · 8 comments

fatal error: sync: Unlock of unlocked RWMutex

goroutine 1 [running]:
sync.fatal({0x5577813464?, 0x0?})
runtime/panic.go:1031 +0x20
sync.(*RWMutex).Unlock(0x40000b424c)
sync/rwmutex.go:209 +0x78
code.rocketnine.space/tslocum/cview.(*Application).Init(0x40000b4140)
code.rocketnine.space/tslocum/cview@v1.5.6-0.20210530175404-7e8817f20bdc/application.go:226 +0x84
main.main()
github.com/makeworld-the-better-one/amfora/amfora.go:71 +0x544

goroutine 18 [runnable]:
strings.Index({0x557780aeb4, 0x15}, {0x55778a6740, 0x1})
strings/strings.go:1178 +0x558
strings.genSplit({0x557780aeb4, 0x15}, {0x55778a6740, 0x1}, 0x0, 0x400007c150?)
strings/strings.go:251 +0x108
strings.Split(...)
strings/strings.go:305
github.com/spf13/viper.(*Viper).find(0x4000022900, {0x557780aeb4, 0x15}, 0x1)
github.com/spf13/viper@v1.7.1/viper.go:1027 +0x54
github.com/spf13/viper.(*Viper).Get(0x4000022900, {0x557780aeb4?, 0x55778f46e0?})
github.com/spf13/viper@v1.7.1/viper.go:728 +0x48
github.com/spf13/viper.(*Viper).GetInt(0x0?, {0x557780aeb4?, 0x0?})
github.com/spf13/viper@v1.7.1/viper.go:805 +0x20
github.com/spf13/viper.GetInt(...)
github.com/spf13/viper@v1.7.1/viper.go:803
github.com/makeworld-the-better-one/amfora/subscriptions.updateAll()
github.com/makeworld-the-better-one/amfora/subscriptions/subscriptions.go:397 +0xb4
github.com/makeworld-the-better-one/amfora/subscriptions.Init.func1()
github.com/makeworld-the-better-one/amfora/subscriptions/subscriptions.go:78 +0x1c
created by github.com/makeworld-the-better-one/amfora/subscriptions.Init
github.com/makeworld-the-better-one/amfora/subscriptions/subscriptions.go:76 +0x2e0

Please let me know what version of Amfora you are running with the output of amfora -v. If you are able, please try to compile a binary from the latest commit on the master branch, to see if you still get the crash there.

Also instructions on what caused the crash will be needed.

This looks the same as #300, so I would recommend a fix from that thread: install ncurses on your machine. If that works, I will close this issue, as #300 remains open.

Hmm ok thanks. Can you make sure you have ncurses-terminfo installed as well? And what terminal are you using?

Ok, thanks! Glad to hear you got it working in some fashion. I will close this issue for now but you can reopen it if needed. And merry Christmas if you celebrate!