Comments on Crashing while running Twitter

Last edit

Summary: Done!


> ----
> [ Done]!
> -- Alex Schroeder 2019-08-30 15:14 UTC

As mentioned on IRC, the order seems to matter. I wonder whether there us some leakage between Twitter and Mastodon data structures. The Mastodon code was originally a copy of the Twitter code. Are we freeing data that is held by Twitter or is Twitter doing it to us? Are we redefining structures that no longer work for Twitter once we initialize them?

What would be cool is a git bisect to see whether this worked in the past and to find the commit that broke it.

– Alex Schroeder 2019-05-03 12:07 UTC

Also from IRC, user mcepl posted this:, suggesting something about filters.

– Alex Schroeder 2019-05-03 12:27 UTC

dx reposted user tramtrist's crash report: and noted that it was crashing here:

– Alex Schroeder 2019-05-03 12:27 UTC

Link 3862:

g_slist_free_full(mud->lists, g_free); mud->lists = NULL;

Lines referring to lists:

grep --color -niH -e '->lists' *.c
mastodon.c:871:	g_slist_free_full(mud->lists, g_free); mud->lists = NULL;
mastodon-lib.c:959:		for (l = mud->lists; l; l = l->next) {
mastodon-lib.c:3812:			mud->lists = g_slist_prepend(mud->lists, g_strdup(mc->str));
mastodon-lib.c:3862:			g_slist_free_full(mud->lists, g_free); mud->lists = NULL;

I can't see anything strange about the code.

– Alex Schroeder 2019-05-03 16:22 UTC

I see the same behaviour. Shutting down the Twitter account, starting Mastodon, then starting Twitter helps.

Could you mention this in the README/setup docs? I suspect I'm not the only one who was kept away from using this client and/or Mastodon by assuming that the plugin was simply not working.

rixx 2019-08-30 10:56 UTC


– Alex Schroeder 2019-08-30 15:14 UTC

This wiki uses a variant of Markdown.

To save this page you must answer this question:

Please write "new issue" into the field below.