Segmentation violation on HandleMessage

[forthommel]

Dear developers,

First, let me thank you a lot for this bridge! It has been very useful so far.

However, I am encountering issues at bridge startup (as if the user/password storage in DB introduced in #14 does not work properly): I need to manually regenerate the connection token.
Furthermore, after an umpteenth of these (where all latest conversation pop up all at once in a fantastic notifications firework) it looks like the first messages display in a conversation is unevitably leading to this segfault:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x87a7ea]

goroutine 285 [running]:
maunium.net/go/mautrix/appservice.(*IntentAPI).EnsureJoined(0x0, {0xc000029f50, 0x27})
	/opt/go-skype-bridge/go/pkg/mod/github.com/pidongqianqian/mautrix-go@v0.10.4-0.20211208080648-321c4f849adb/appservice/intent.go:70 +0x2a
maunium.net/go/mautrix/appservice.(*IntentAPI).RedactEvent(0x0, {0xc000029f50, 0x27}, {0xc000029f20, 0x2c}, {0x0, 0x0, 0x0})
	/opt/go-skype-bridge/go/pkg/mod/github.com/pidongqianqian/mautrix-go@v0.10.4-0.20211208080648-321c4f849adb/appservice/intent.go:226 +0x4b
main.(*MatrixHandler).HandleMessage.func1()
	/opt/go-skype-bridge/matrix.go:405 +0x88
created by main.(*MatrixHandler).HandleMessage
	/opt/go-skype-bridge/matrix.go:402 +0x2ec

Could you please have a look and see if something requires a bit more attention?

Thanks in advance!
L.F.

[czen]

Encountered the same issue. Bridge synced a lot of personal and group chats, then crashed with this errror. Every restart and login now leads to the same error.

[forthommel]

Same for me, and as no update was made on this ticket I completely (and sadly) dropped this solution.

[aostanin]

I encountered this same issue and was able to work around it by removing these lines from matrix.go:

go-skype-bridge/matrix.go

Lines 401 to 410 in 59e2790

	if strings.HasPrefix(content.Body, "login") == true {
	go func() {
	time.Sleep(time.Second * 10)
	customPuppet := user.bridge.GetPuppetByJID(user.JID)
	_, err := customPuppet.customIntent.RedactEvent(evt.RoomID, evt.ID)
	if err != nil {
	mx.log.Debugfln("HandleMessage RedactEvent: %+v", err)
	}
	}()
	}

The bot waits for 10 seconds after login then tries to remove the login message with your username and password from the chat history. That's where the crash occurs. I don't know the root cause, but at least this workaround makes the bridge usable.