Plugin causes frequent Pidgin crashes

[LurkerHub]

Every now and then, the plugin loses connection to the server, and then, when it tries to reconnect, crashes Pidgin.
Restarting Pidgin often causes another crash.

Example crash reports.

Error occured on Saturday, August 14, 2021 at 10:42:48.

Windows Version 10.0 Build 19042 

C:\Program Files (x86)\Pidgin\pidgin.exe caused an Access Violation at location 03951504 in module C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll Reading from location 00000058.

Registers:
eax=00000000 ebx=00000000 ecx=077d0c40 edx=077d0c40 esi=00000009 edi=0ef64b28
eip=03951504 esp=007fe80c ebp=007fe868 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202

Call stack:
         C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll [1.4.7.0]
03951504 C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll
0396CA36 C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll  purple_init_plugin
03970E7C C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll  purple_init_plugin
03971322 C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll  purple_init_plugin
0395251D C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll
         C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll [2.28.8.0]
         Using Debug Symbols from: C:\Program Files (x86)\Pidgin\pidgin-2.14.6-dbgsym\Gtk\bin\libglib-2.0-0.dll.dbgsym
685EB167 C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
685EB90D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
685EBD9D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_loop_run
         C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll [2.16.6.0]
         Using Debug Symbols from: C:\Program Files (x86)\Pidgin\pidgin-2.14.6-dbgsym\Gtk\bin\libgtk-win32-2.0-0.dll.dbgsym
61854260 C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll  gtk_main

-------------------

Error occured on Saturday, August 14, 2021 at 16:18:38.

Windows Version 10.0 Build 19042 

C:\Program Files (x86)\Pidgin\pidgin.exe caused an Access Violation at location 04311504 in module C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll Reading from location 00000058.

Registers:
eax=00000000 ebx=00000000 ecx=114a5690 edx=114a5690 esi=00000009 edi=103919b0
eip=04311504 esp=011fe4ec ebp=011fe548 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206

Call stack:
         C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll [1.4.7.0]
04311504 C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll
0432C200 C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll  purple_init_plugin
0431251D C:\Program Files (x86)\Pidgin\plugins\libtelegram.dll
         C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll [2.28.8.0]
         Using Debug Symbols from: C:\Program Files (x86)\Pidgin\pidgin-2.14.6-dbgsym\Gtk\bin\libglib-2.0-0.dll.dbgsym
685EB167 C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
685EB90D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_context_dispatch
685EBD9D C:\Program Files (x86)\Pidgin\Gtk\bin\libglib-2.0-0.dll  g_main_loop_run
         C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll [2.16.6.0]
         Using Debug Symbols from: C:\Program Files (x86)\Pidgin\pidgin-2.14.6-dbgsym\Gtk\bin\libgtk-win32-2.0-0.dll.dbgsym
61854260 C:\Program Files (x86)\Pidgin\Gtk\bin\libgtk-win32-2.0-0.dll  gtk_main

[BenWiederhake]

:/ Sorry to hear that. The instability is nearly always due to libtgl, which is outdated, slow, and was never meant to handle this amount of load. Since no maintainence goes into libtgl or telegram-purple, your best bet is to try out tdlib-purple. In fact, where could I have written this recommendation so that you could have seem a link to tdlib-purple earlier?

[LurkerHub]

Snark aside, "this amount of load" in my case was never higher than a couple of messages a minute.
That said, I *have* switched to tdlib-purple solely because of this issue. If it was not for crashes, I found telegram-purple better behaved.