Pidgin

Ticket #5662 (closed defect)

Opened 2 years ago

Last modified 14 months ago

Search Log crash

Reported by: dave1g Owned by: datallah
Milestone: 2.5.5 Component: winpidgin (gtk)
Version: 2.4.1 Keywords: cairo_surface_set_device_offset
Cc: rlaager, Universe_JDJ, ejallison, agraham

Description

I searched the logs with someone for the word email, many logs files matched, as I clicked around on the files after 4 or 5 pidgin crashed, and then again when I did the same thing.

If it helps, this person has 5 MB of logs with me across 123 files.

Attachments

log_bug.zip (198.7 kB) - added by dave1g 2 years ago.
2 debug logs files and 2 crasheds in one rpt file
pidgin-new-cairo.RPT (2.8 kB) - added by dave1g 2 years ago.
crash with new cairo lib
04-29-2008_22.57.48.23.log (49.0 kB) - added by dave1g 2 years ago.
debug log with new cairo... doesnt look like anything changed
GraficError.JPG (66.4 kB) - added by IlRazziatore 2 years ago.
Graphic errore before crash
NormalGraphic.jpg (101.1 kB) - added by IlRazziatore 2 years ago.
The same window without graphic error…
pidgin.RPT (2.9 kB) - added by dave1g 2 years ago.
pidgin 2.5.1 rpt
09-12-2008_16.35.11.46.log (42.0 kB) - added by dave1g 2 years ago.
pidgin.log with GDK_DEBUG=events:misc
pidgin.2.RPT (16.4 kB) - added by chriswaz 18 months ago.
Crash Report on Vista(x64)

Change History

Changed 2 years ago by dave1g

2 debug logs files and 2 crasheds in one rpt file

  Changed 2 years ago by datallah

  • keywords cairo_surface_set_device_offset added; log crash removed

This is crashing in libcairo (part of the GTK+ runtime). I've seen a crash with a similar stack a number of times - it is a bug in cairo, but I don't know more details than that.

You can try a newer version of cairo by downloading it here and replacing the libcairo-2.dll in the C:\Program Files\Common Files\GTK\2.0\bin directory.

  Changed 2 years ago by datallah

  • pending changed from 0 to 1

Changed 2 years ago by dave1g

crash with new cairo lib

Changed 2 years ago by dave1g

debug log with new cairo... doesnt look like anything changed

  Changed 2 years ago by dave1g

  • pending changed from 1 to 0

was a bit harder to cause this time, i had to click around much longer and much faster. but finally got it to crash, the scrolling of the window down to the searched for word seemed a little faster.

  Changed 2 years ago by dave1g

filed bug with Cairo people

https://bugs.freedesktop.org/show_bug.cgi?id=15761

  Changed 2 years ago by IlRazziatore

I have the same problem with 2.4.2. Sometime if i close the Istant Message Window pidgin don't crash... i save it...

  Changed 2 years ago by IlRazziatore

When i don't save Pidgin form crash this is the log ( pidgin.PPT ) 

Error occured on Saturday, May 17, 2008 at 12:47:50.

Windows Version 5.1 Build 2600 Service Pack 2

C:\Programmi\Pidgin\pidgin.exe caused an Access Violation at location 6c374635 in module C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll Reading from location 0000005c.

Registers:
eax=00000000 ebx=00000000 ecx=00000001 edx=00000000 esi=00d8d408 edi=00d8d408
eip=6c374635 esp=0022e400 ebp=0022e458 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206

Call stack:
         C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.8.0]
6C374635 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_win32_hdc_get
6C365785 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_drag_drop_succeeded
6C366E1C C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_drag_drop_succeeded
6C34395D C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_draw_rectangle
6C34395D C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_draw_rectangle
6C359942 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_get_internal_paint_info
6C34395D C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_draw_rectangle
62D41E61 C:\Programmi\Common Files\GTK\2.0\lib\gtk-2.0\2.10.0\engines\libwimp.dll
62D4218F C:\Programmi\Common Files\GTK\2.0\lib\gtk-2.0\2.10.0\engines\libwimp.dll
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
617BD2D1 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_check_menu_item_get_draw_as_radio
617BCFDD C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_check_menu_item_get_draw_as_radio
6188C522 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_marshal_VOID__UINT_STRING
         C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll [2.14.6.0]
63A43945 C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_closure_invoke
63A56D56 C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_signal_has_handler_pending
63A57C2C C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_signal_emit_valist
63A58166 C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_signal_emit
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
619BE564 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_widget_activate
617EAB22 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_container_propagate_expose
617EAB63 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_container_propagate_expose
618A039E C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_menu_shell_select_item
617E8A00 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_container_forall
617EA741 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_container_get_focus_hadjustment
6189343B C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_menu_reorder_child
6188C522 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_marshal_VOID__UINT_STRING
         C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll [2.14.6.0]
63A43945 C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_closure_invoke
63A56D56 C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_signal_has_handler_pending
63A57C2C C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_signal_emit_valist
63A58166 C:\Programmi\Common Files\GTK\2.0\bin\libgobject-2.0-0.dll  g_signal_emit
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
619BE564 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_widget_activate
6188ACE4 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_main_do_event
         C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.8.0]
6C35C4C3 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_clear_area_e
6C35C608 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_process_all_updates
6C35C62B C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_process_all_updates
6C3417E8 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_threads_set_lock_functions
         C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll [2.14.6.0]
685DE887 C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_context_dispatch
685DFD6B C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_context_acquire
685DFF5A C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_loop_run
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
61889F3E C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_main
         C:\Programmi\Pidgin\pidgin.dll [2.4.1.0]
64A8DED1 C:\Programmi\Pidgin\pidgin.dll  pidgin_main  c:/devel/pidgin-devel/pidgin-2.4.1/pidgin/gtkmain.c:887
         C:\Programmi\Pidgin\pidgin.exe [2.4.1.0]
00402182 C:\Programmi\Pidgin\pidgin.exe  WinMain  c:/devel/pidgin-devel/pidgin-2.4.1/pidgin/win32/winpidgin.c:658
004025BA C:\Programmi\Pidgin\pidgin.exe  WinMain  c:/devel/pidgin-devel/pidgin-2.4.1/pidgin/win32/winpidgin.c:448
00401247 C:\Programmi\Pidgin\pidgin.exe
004012B8 C:\Programmi\Pidgin\pidgin.exe
         C:\WINDOWS\system32\kernel32.dll [5.1.2600.2180]
7C816D4F C:\WINDOWS\system32\kernel32.dll  RegisterWaitForInputIdle

more log of normal: 

Error occured on Sunday, May 25, 2008 at 02:03:22.

Windows Version 5.1 Build 2600 Service Pack 2

C:\Programmi\Pidgin\pidgin.exe caused an Access Violation at location 67ad44ff in module C:\Programmi\Common Files\GTK\2.0\bin\libcairo-2.dll Reading from location 000000ac.

Registers:
eax=00000000 ebx=025fd788 ecx=ffffffff edx=ffffff97 esi=027845c0 edi=10f6bc88
eip=67ad44ff esp=0022f1b0 ebp=0022f1c8 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210202

Call stack:
67AD44FF C:\Programmi\Common Files\GTK\2.0\bin\libcairo-2.dll  cairo_surface_set_device_offset
         C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.8.0]
6C35B347 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_begin_paint_region
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
6188ACD8 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_main_do_event
         C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.8.0]
6C35C4C3 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_clear_area_e
6C35CC0D C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_window_process_updates
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
61865809 C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_image_get
         C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.8.0]
6C3417E8 C:\Programmi\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll  gdk_threads_set_lock_functions
         C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll [2.14.6.0]
685E0B96 C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_context_is_owner
685DE887 C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_context_dispatch
685DFD6B C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_context_acquire
685DFF5A C:\Programmi\Common Files\GTK\2.0\bin\libglib-2.0-0.dll  g_main_loop_run
         C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.8.0]
61889F3E C:\Programmi\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll  gtk_main
         C:\Programmi\Pidgin\pidgin.dll [2.4.2.0]
64A8EE01 C:\Programmi\Pidgin\pidgin.dll  pidgin_main  c:/devel/pidgin-devel/pidgin-2.4.2/pidgin/gtkmain.c:897
         C:\Programmi\Pidgin\pidgin.exe [2.4.2.0]
00402182 C:\Programmi\Pidgin\pidgin.exe  WinMain  c:/devel/pidgin-devel/pidgin-2.4.2/pidgin/win32/winpidgin.c:658
004025BA C:\Programmi\Pidgin\pidgin.exe  WinMain  c:/devel/pidgin-devel/pidgin-2.4.2/pidgin/win32/winpidgin.c:448
00401247 C:\Programmi\Pidgin\pidgin.exe
004012B8 C:\Programmi\Pidgin\pidgin.exe
         C:\WINDOWS\system32\kernel32.dll [5.1.2600.2180]
7C816D4F C:\WINDOWS\system32\kernel32.dll  RegisterWaitForInputIdle

This is only bug of winpidgin?

  Changed 2 years ago by dave1g

what do you mean by "saving it"?

how do you cause the first crash differently from the second one?

  Changed 2 years ago by IlRazziatore

with "save it" i mean pidgin start crash ( the contact list disapair... the IM Windows have some grafic error ecc ecc )... but if i close the IM window... pidgin don't crash return normal...

you understend now?

Some times i don't do it in time and... it crash with the first log

  Changed 2 years ago by IlRazziatore

Crash is realy frequently when i chat with friend... when i not at PC it dont crash... but if i at the PC.

From the 15 May to 25 May i have 30 crash ( avarange: 3 crash/day ) but some day it dont crash other... 

Error occured on Wednesday, May 21, 2008 at 00:28:54.
Error occured on Wednesday, May 21, 2008 at 12:04:53.
Error occured on Wednesday, May 21, 2008 at 13:03:57.
Error occured on Wednesday, May 21, 2008 at 18:13:43.
Error occured on Wednesday, May 21, 2008 at 19:55:03.
Error occured on Wednesday, May 21, 2008 at 20:39:40.
Error occured on Wednesday, May 21, 2008 at 21:33:04.
Error occured on Wednesday, May 21, 2008 at 21:42:27.
Error occured on Wednesday, May 21, 2008 at 21:55:07.
Error occured on Wednesday, May 21, 2008 at 23:09:42.
Error occured on Wednesday, May 21, 2008 at 23:35:51.

When you stay chatting with your friend and pigdin crash frequenty isnt good...

follow-up: ↓ 11   Changed 2 years ago by dave1g

But then after you save it, it still crashes eventually producing a pidgin.rpt, correct? Does this just eventually happen, or do you do something to trigger it?

Also it might be useful to see the debug log as well (in both cases) by using pidgin -d > pidgin.log to start pidgin or you can use my ready made script here TipsForBugReports#PreemptiveDebugLogging the log just prints out various log traces scattered throughout pidgin, things like "sending im", "window maximized" etc.

Also please read #5593 as that bug is similar to mine except there are graphic artifacts like you describe.

in reply to: ↑ 10   Changed 2 years ago by IlRazziatore

Replying to dave1g:

But then after you save it, it still crashes eventually producing a pidgin.rpt, correct? Does this just eventually happen, or do you do something to trigger it?

Yes. If it crash it crash producing a pidgin.rpt... sometimes i save it sametimes no. I don't know why... i supose i don't close the window imidiatly...

If i close the window imidiatly and i save pidgin sucessful i can reopen the window and continue chating... waiting the next crash...

Also it might be useful to see the debug log as well (in both cases) by using pidgin -d > pidgin.log to start pidgin or you can use my ready made script here TipsForBugReports#PreemptiveDebugLogging the log just prints out various log traces scattered throughout pidgin, things like "sending im", "window maximized" etc.

Okay, the next time pidgin crash i open it with the script.

Also please read #5593 as that bug is similar to mine except there are graphic artifacts like you describe.

Uhmm #5593? I see the grafic error... i have an other type... when it crash again i create a Screenshot...

The problem is if i don't chat it don't crash :P

  Changed 2 years ago by dave1g

Running using the script after the crash wont help, you will need to just always run it using the script so that when it does crash all of your activity has been logged to provide further clues.

It sounds like the 4 of us, on the 2 tickets all have crashes that have the same root cause, some gtk bug in the Cairo screen drawing infrastructure, but we all have different symptoms and different ways of causing it.

Also, for the rpt and debug log files, its probably best to just add them as attachments to the ticket instead of posting them inline, since they are easier to read that way.

Changed 2 years ago by IlRazziatore

Graphic errore before crash

Changed 2 years ago by IlRazziatore

The same window without graphic error...

  Changed 2 years ago by IlRazziatore

Some news?

  Changed 2 years ago by IlRazziatore

I found the problem or maybe i found a workaround.

I discover the crash is casused by personal smiels form MSN. When someone use a personal smiles ( animeted i supose ) pidgin crash. Not the first time, not the second but it crash.

I disable the smies ( Preferences -> Smiles ) and pidgin stop crash...

I supose the problem is a memory allocation of the incoming smiles. If i use only standard pidgin don't crash!

  Changed 2 years ago by dave1g

my testing was always with an aim user

  Changed 2 years ago by dave1g

I can cause this crash without even searching for a word. slowly click between 2 logs switching back and forth, memory use rises 1-3 megs on each click, then eventually pidgin crashes

  Changed 2 years ago by IlRazziatore

I try the new version ( Pidgin 2.4.3 ) and it crash too :(

  Changed 2 years ago by dave1g

I think I have identified the exact problem with GTK/Cairo. Details on their trackers.

When the GTK and Cairo bugs listed are fixed, these pidgin/gaim tickets should be hopefully all be resolved as well

GTK bug - http://bugzilla.gnome.org/show_bug.cgi?id=543209

Cairo bug - http://bugs.freedesktop.org/show_bug.cgi?id=15761

Pidgin/gaim bugs: #5662 #5893 #4826 #5593 #5594 #6252

Mirror of old gaim sourceforge tracker: http://article.gmane.org/gmane.comp.gnome.gaim.bugs/175

  Changed 2 years ago by IlRazziatore

I hope GTK/Cairo fix the problem...

follow-up: ↓ 21   Changed 2 years ago by mcsmccomb

Found a fix that worked on my machine. 1. Uninstall Pidgin and delete all Pidgin directories 2. Uninstall GTK+ and its associated directories 3. Remove the C:/Documents and Settings/%user%/Application data/.purple directory. 4. Reboot 5. Reinstalled Pidgin 2.4.3 with GTK+

After that it worked fine for me. Hope the info helps. Not sure what the bug is, but that got it working on my box.

in reply to: ↑ 20   Changed 2 years ago by datallah

Replying to mcsmccomb:

Found a fix that worked on my machine.

Of course it did, you deleted all your logs! It'll come back when you've gotten some logs.

  Changed 2 years ago by GrayFox777

This problem still isn't fixed in 2.5.1. But I guess that's probably cause it's a GTK/Cairo problem.

  Changed 2 years ago by datallah

Ticket #6970 has been marked as a duplicate of this ticket.

  Changed 2 years ago by datallah

Ticket #5523 has been marked as a duplicate of this ticket.

  Changed 2 years ago by datallah

Can someone run the following from the command line and attach the "pidgin.log" after it crashes (and leave a comment on the ticket too): 

cd "c:\Program Files\Pidgin"

set GDK_DEBUG=events:misc

pidgin.exe -d 2>&1 > pidgin.log

Changed 2 years ago by dave1g

pidgin 2.5.1 rpt

Changed 2 years ago by dave1g

pidgin.log with GDK_DEBUG=events:misc

  Changed 2 years ago by dave1g

request fulfilled.

  Changed 22 months ago by datallah

Ticket #7413 has been marked as a duplicate of this ticket.

  Changed 22 months ago by ejallison

Experiencing this problem with 2.5.2, never have before to my knowledge.

Sometimes it displays a zoomed-in portion of a message (around 2000%, all I can see is half the time stamp) in the message pane right before it dies.

Here's the .RPT, it appears to be a problem with cairo...

Error occured on Thursday, October 30, 2008 at 00:45:44.

Windows Version 6.0 Build 6001 Service Pack 1

C:\Program Files\Pidgin\pidgin.exe caused an Access Violation at location 68dd6cff in module C:\Program Files\Common Files\GTK\2.0\bin\libcairo-2.dll Reading from location 000000bc.

Registers: eax=00000000 ebx=1396e848 ecx=77ad9d78 edx=00000000 esi=0b4d7c18 edi=15ef1c48 eip=68dd6cff esp=0022ef40 ebp=0022ef58 iopl=0 nv up ei pl nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210202

Call stack: 68DD6CFF C:\Program Files\Common Files\GTK\2.0\bin\libcairo-2.dll cairo_surface_set_device_offset

C:\Program Files\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.12.0]

6C35B347 C:\Program Files\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll gdk_window_begin_paint_region

C:\Program Files\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.12.0]

6188A4E8 C:\Program Files\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll gtk_main_do_event

C:\Program Files\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll [2.12.12.0]

6C35C4C3 C:\Program Files\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll gdk_window_clear_area_e 6C35CBDD C:\Program Files\Common Files\GTK\2.0\bin\libgdk-win32-2.0-0.dll gdk_window_process_updates 6B6C41DC C:\Program Files\Pidgin\plugins\guifications.dll gf_display_animate /home/jbailey/devel/win32xcompile/pidgin200/pidgin/plugins/pidgin-guifications-2.16/src/gf_display.c:875

C:\Program Files\Common Files\GTK\2.0\bin\libglib-2.0-0.dll [2.16.6.0]

685E9396 C:\Program Files\Common Files\GTK\2.0\bin\libglib-2.0-0.dll g_main_context_is_owner 685E7077 C:\Program Files\Common Files\GTK\2.0\bin\libglib-2.0-0.dll g_main_context_dispatch 685E854B C:\Program Files\Common Files\GTK\2.0\bin\libglib-2.0-0.dll g_main_context_acquire 685E873A C:\Program Files\Common Files\GTK\2.0\bin\libglib-2.0-0.dll g_main_loop_run

C:\Program Files\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll [2.12.12.0]

6188974E C:\Program Files\Common Files\GTK\2.0\bin\libgtk-win32-2.0-0.dll gtk_main

C:\Program Files\Pidgin\pidgin.dll [2.5.2.0]

64A906C1 C:\Program Files\Pidgin\pidgin.dll pidgin_main c:/devel/pidgin-devel/pidgin-2.5.2/pidgin/gtkmain.c:895

C:\Program Files\Pidgin\pidgin.exe [2.5.2.0]

00402362 C:\Program Files\Pidgin\pidgin.exe WinMain?? c:/devel/pidgin-devel/pidgin-2.5.2/pidgin/win32/winpidgin.c:736 004029AA C:\Program Files\Pidgin\pidgin.exe WinMain?? c:/devel/pidgin-devel/pidgin-2.5.2/pidgin/win32/winpidgin.c:523 00401247 C:\Program Files\Pidgin\pidgin.exe 004012B8 C:\Program Files\Pidgin\pidgin.exe

C:\Windows\system32\kernel32.dll [6.0.6001.18000]

764F4911 C:\Windows\system32\kernel32.dll BaseThreadInitThunk??

C:\Windows\system32\ntdll.dll [6.0.6001.18000]

77C8E4B6 C:\Windows\system32\ntdll.dll RtlInitializeExceptionChain??

  Changed 22 months ago by datallah

Ticket #7451 has been marked as a duplicate of this ticket.

follow-up: ↓ 31   Changed 22 months ago by Bluedeep

6 months ???

Guys, i love really pidgin... But it crash too often ...

So i'll switch back to messanger.

in reply to: ↑ 30   Changed 22 months ago by craz

I recently had something like this same bug, message window text zooming in followed by crash. Turning off event logging seems to have stopped my crashes, been ok for 2 days now.

(not sure where else to post this)

  Changed 21 months ago by datallah

Ticket #7804 has been marked as a duplicate of this ticket.

  Changed 21 months ago by zenomcdohl

This does not happen just with logs/search. I'm just IMing and it happens. Using latest version (2.5.2)

  Changed 21 months ago by datallah

Ticket #7828 has been marked as a duplicate of this ticket.

  Changed 21 months ago by maruchan

Yeah I agree, the problem is with smilies... the reason why I said it's an asian invasion is cuz all the asian ppl use that stuff when they chat and it crashes my pidgin at least 2-3 times a day...

  Changed 20 months ago by datallah

Ticket #7897 has been marked as a duplicate of this ticket.

  Changed 20 months ago by zenomcdohl

Turning off smilies doesn't fix this. I've had smilies off for months, still getting daily crashes.

  Changed 20 months ago by dave1g

If you want this fixed then you need to lobby the GTK people at http://bugzilla.gnome.org/show_bug.cgi?id=543209 Their software has the bug, not pidgin. I have pointed out to them exactly what they are doing wrong, but it seems no one there cares enough to actually fix it in their code base.

  Changed 20 months ago by dave1g

pidgin is leaking lots of GDI

http://bugzilla.gnome.org/show_bug.cgi?id=543209#c8

atleast 2 on every im window open.

~200 each time you open the log viewer window

10-100 on each click to a different log file in the log viewer

follow-up: ↓ 45   Changed 20 months ago by dave1g

Fixed in pango 1.22? seems fixed for me.

please try to download Pango 1.22.4 binaries from here http://www.gtk.org/download-windows.html

close pidgin, copy the dlls from the bin dir in the zip file to C:\Program Files\Common Files\GTK\2.0\bin

or wherever you have gtk installed. start up pidgin again. gdi use doesnt grow anymore when clicking around in log viewer

http://bugzilla.gnome.org/show_bug.cgi?id=543209#c9

  Changed 19 months ago by QuLogic

Ticket #6602 has been marked as a duplicate of this ticket.

  Changed 19 months ago by QuLogic

Ticket #8313 has been marked as a duplicate of this ticket.

  Changed 19 months ago by deryni

Ticket #8365 has been marked as a duplicate of this ticket.

  Changed 19 months ago by datallah

Ticket #8389 has been marked as a duplicate of this ticket.

in reply to: ↑ 40   Changed 19 months ago by nagelp

Replying to dave1g:

Fixed in pango 1.22? seems fixed for me.

For me, too. FINALLY.

David, thanks a lot for reporting and tracking down this nasty bug, it caused multiple crashes per day for some of our users... (which didn't help much in promoting Pidgin's reputation amongst the employees, as you can imagine).

follow-up: ↓ 47   Changed 19 months ago by rlaager

Daniel, can we ship Pango 1.22 with the next Pidgin release or do we need to wait for that to end up in a GTK+ installer?

in reply to: ↑ 46 ; follow-up: ↓ 48   Changed 19 months ago by datallah

Replying to rlaager:

Daniel, can we ship Pango 1.22 with the next Pidgin release or do we need to wait for that to end up in a GTK+ installer?

Lets plan to release an updated GTK+ installer with the next release with 1.22.4. However, according to the responses on some other tickets, it will not necessarily resolve all the cairo_surface_set_device_offset related crashes that have been reported.

in reply to: ↑ 47   Changed 19 months ago by dave1g

Replying to datallah:

Replying to rlaager:

Daniel, can we ship Pango 1.22 with the next Pidgin release or do we need to wait for that to end up in a GTK+ installer?

Lets plan to release an updated GTK+ installer with the next release with 1.22.4. However, according to the responses on some other tickets, it will not necessarily resolve all the cairo_surface_set_device_offset related crashes that have been reported.

which ones haven't been fixed?

by the way #5618 should probably be marked a dupe as well.

#5633 is the only one that looks like it but the comment is 9 months old.

Would be nice if dupes were closed for editing and users attempting to post would be directed to post to the master bug unless set back to a non closed state.

follow-up: ↓ 50   Changed 19 months ago by agraham

I've been getting the libcairo crash off and on for as long as I've used Pidgin. The latest version crashes about every other day which is much better than some earlier versions. Lately I turned on the "GDI Objects" column in Task Manager and looked at it when Pidgin crashes. The crash always occurs when Pidgin has allocated 9,999 GDI objects. The per-process limit in Windows XP is 10,000 GDI objects. I don't imagine this is a coincidence.

in reply to: ↑ 49   Changed 19 months ago by dave1g

Replying to agraham:

I've been getting the libcairo crash off and on for as long as I've used Pidgin. The latest version crashes about every other day which is much better than some earlier versions. Lately I turned on the "GDI Objects" column in Task Manager and looked at it when Pidgin crashes. The crash always occurs when Pidgin has allocated 9,999 GDI objects. The per-process limit in Windows XP is 10,000 GDI objects. I don't imagine this is a coincidence.

you are correct there is a 10k per process limit in windows. did you download and install the latest libpango library?

  Changed 18 months ago by agraham

Ah. No... I hadn't read the latest posts. Installed it now. The GDI leaking seems to be gone. Will report back if it crashes again, but I betcha that fixed it.

Changed 18 months ago by chriswaz

Crash Report on Vista(x64)

  Changed 18 months ago by datallah

Ticket #8519 has been marked as a duplicate of this ticket.

  Changed 18 months ago by deryni

Ticket #8555 has been marked as a duplicate of this ticket.

  Changed 18 months ago by datallah

  • status changed from new to pending
  • milestone set to 2.5.5

2.5.5 shipped with GTK+ 2.14.7 containing Pango 1.22.4, which fixes the GDI leak.

Hopefully that should resolve this issue.

  Changed 18 months ago by trac-robot

  • status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

  Changed 16 months ago by datallah

Ticket #9056 has been marked as a duplicate of this ticket.

  Changed 16 months ago by ruv

Bug still exist in Pidgin 2.5.5 (see #9056)

  Changed 14 months ago by darkrain42

Ticket #6585 has been marked as a duplicate of this ticket.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!