Skip to content
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

Open
Vaelatern opened this issue Feb 26, 2018 · 5 comments
Open

Can segfault #9

Vaelatern opened this issue Feb 26, 2018 · 5 comments
Labels

Comments

@Vaelatern
Copy link

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

@abenson abenson added the bug label Feb 26, 2018
abenson added a commit that referenced this issue Mar 13, 2018
abenson added a commit that referenced this issue Apr 11, 2018
@Vaelatern
Copy link
Author

I am testing the latest code on the same platform. No segfaults yet, will report back.

@Vaelatern
Copy link
Author

Does not regularly, but after several days of use one of my three instances did segfault.

@Vaelatern Vaelatern reopened this Apr 22, 2018
@Vaelatern
Copy link
Author

And again on a different instance, possibly related to uptime of the instance?

@Vaelatern
Copy link
Author

No messages drop, so though it triggers on message receives, it completes receiving the message and printing it before it segfaults.

@Vaelatern
Copy link
Author

Also has been triggered by sending a message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants