-
Notifications
You must be signed in to change notification settings - Fork 61
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
Segmentation fault on login #535
Comments
Login is also extraordinarily slow, taking over two minutes prior to the segfault:
Maybe this is something to do with having so many users? |
Can you try with the latest version first? 0.27.0 or better yet, build from trunk/master? |
It's possible. I'm trying to reproduce it, but sadly don't have access to a Mattermost server with close to 60k users. The community Mattermost server ( |
I also have the crash / segfault. Just before the segfault occurs I could see something like this before it crashed
That occurred when I ran this command:
I noticed the team is wrong. To rectify I did this:
Where technology is the team name. The software then didn't crash and |
@divansantana please paste the segfault and version of matterircd used |
Revisiting this.
So this is fallout from #491 where it's doing more calls to get the correct no. of users in the team. The Mattermost API limits each to 200 so it takes quite a lot of calls to get to 59032 users. I wonder if it's actually the no. of channels instead? With 59k users, I'm sure there's a boat load more channels. Though from looking at the matterclient code, it should have printed |
Hi! Thanks for building this. I tried to log in to a Mattermost instance, and shortly afterwards matterircd 0.26.1 crashed with this traceback:
Obviously since it's the login, not much more I can share, but I'm not aware of doing anything too weird.
The text was updated successfully, but these errors were encountered: