-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can segfault #9
Comments
I am testing the latest code on the same platform. No segfaults yet, will report back. |
Does not regularly, but after several days of use one of my three instances did segfault. |
And again on a different instance, possibly related to uptime of the instance? |
No messages drop, so though it triggers on message receives, it completes receiving the message and printing it before it segfaults. |
Also has been triggered by sending a message |
This is the third error I noticed. I'm sorry this one is so vague.
I triggered a segfault by copy and pasting a complete previous line as a message:
[2018-02-26 03:04:50] <Usernme> Every line is starting with a bunch of question marks in white diamonds
Line length is unaltered, the username is changed. Total line length is 133 characters. I could not replicate the error by sending the same message again.
Should mention that I built commit f44ff3e
The text was updated successfully, but these errors were encountered: