Daniel Jay Haskin

That is interesting, but it doesn't crash when I leave everything else on. That said, I'll get you that traceback soon. I'll also shut off all other plugins and see...

I got it to happen again, this time with the only plugin being on was slack-libpurple. Gist with anonymized data for the slack-plugin-only run here: https://gist.github.com/djhaskin987/15db6dae6e27c50d9095c1aa99e76247 Here's a gist with...

EDIT: Please disregard the following backtrace, it isn't the right one. I gave the wrong one because apport only keeps one backtrace at a time, and so I thought this...

I apologize, that's not the right backtrace at *all*. It was a mix-up. I'll get you the right one.

Got the correct backtrace. Here it is: ``` 0 43:07 ~/C/t/p/pidgincrash $ gdb /usr/bin/pidgin CoreDump GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU...

I'm using the following diff to try to fix the issue. I don't know what I'm doing, but basically I'm storing the channel and account in `SlackChatBuddy`, rather than the...

That extra `g_free` I added was problematic. Caused a double-free, oopz. I'm still testing :)

If you want to follow along at home with my tests, they are here: https://github.com/djhaskin987/slack-libpurple/tree/bugfix/crashing-and-memory That branch contains my fixes but also it contains the find-user hack so I could...

Tests went well. I submitted a PR with my changes in #179 :)

The time I was able to log in without lazy loading enabled, I was able to see all the users in the room, and all the display names worked properly...