You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2024. It is now read-only.
What is the problem: Server Crashes infrequently and randomly, the first error before dumping a massive stack trace is: fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)
Who is affected: Users of my server
How is this bug manifesting: log of incident will be sent to @kegan:matrix.org as I'm not sure what in this log, if anything, would reveal information about my HS setup.
When did this first appear: It has been a problem since I've set up this dendrite instance. This is the second instance of this happening, the trace beyond the first fatal error line in the log was different that first time. Unfortunately I accidentally overwrote that log when capturing this new one. If it happens again and more context is needed I'll capture another one.
Steps to reproduce
Start a federated dendrite server
Leave it alone for a while
The text was updated successfully, but these errors were encountered:
I actually created a DM with both users mentioned in the comment of the issue template. Element unfortunately does not clarify that this is just an invite only room, which kegan didn't accept. Neil did, but let me know that they're no longer a contributing member to dendrite. I didn't ask any further (mainly because they left before I noticed their message), but I'm sure they'd appreciate being removed from the template. I'll try a proper DM with kegan one more time, and if nothing else, some other member can drop a comment with their handle.
Background information
go version
:go version go1.21.1 linux/amd64
Description
fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)
fatal error
line in the log was different that first time. Unfortunately I accidentally overwrote that log when capturing this new one. If it happens again and more context is needed I'll capture another one.Steps to reproduce
The text was updated successfully, but these errors were encountered: