[Pidgin] #7317: Pidgin memory allocation grows without limit

[Pidgin]

#7317: Pidgin memory allocation grows without limit
--------------------------+-------------------------------------------------
 Reporter:  helgerustad   |        Owner:              
     Type:  defect        |       Status:  new         
Milestone:                |    Component:  pidgin (gtk)
  Version:  2.5.2         |   Resolution:              
 Keywords:  memory grows  |  
--------------------------+-------------------------------------------------

Comment(by phroggie):

 Changing the GTK+ system theme to something other than MS-Windows seems to
 fix the memory consumption problems, so I think that the wimp theme is at
 fault.

 In an effort to help track it down, (and if you have the GTK bug number
 handy, I'll post this upstream, too): Spying on the desktop with Spy++,
 here's what the display properties dialog does when one hits apply:
 {{{
 <01> 000100AE P WM_PAINT hdc:00000000
 <02> 000100AE S WM_NCPAINT hrgn:00000001
 <03> 000100AE R WM_NCPAINT
 <04> 000100AE S WM_ERASEBKGND hdc:620110DC
 <05> 000100AE S LVM_GETBKCOLOR
 <06> 000100AE R LVM_GETBKCOLOR clrBk:FFFFFFFF
 <07> 000100AE R WM_ERASEBKGND fErased:True
 <08> 000100AE S WM_SETTINGCHANGE wFlag:0000 pszMetrics:0007F804
 <09> 000100AE R WM_SETTINGCHANGE
 <10> 000100AE S WM_SETTINGCHANGE wFlag:0000 pszMetrics:0007FB78
 <11> 000100AE R WM_SETTINGCHANGE
 }}}

 Here's what Wallpaper Master generates, still spying on the desktop:
 {{{
 <01> 000100AE P WM_PAINT hdc:00000000
 <02> 000100AE S WM_NCPAINT hrgn:00000001
 <03> 000100AE R WM_NCPAINT
 <04> 000100AE S WM_ERASEBKGND hdc:C6010D41
 <05> 000100AE S LVM_GETBKCOLOR
 <06> 000100AE R LVM_GETBKCOLOR clrBk:FFFFFFFF
 <07> 000100AE R WM_ERASEBKGND fErased:True
 <08> 000100AE S message:0x1050 [User-defined:WM_USER+3152] wParam:00000000
 lParam:FF000000
 <09> 000100AE R message:0x1050 [User-defined:WM_USER+3152]
 lResult:00000001
 <10> 000100AE S LVM_GETBKCOLOR
 <11> 000100AE R LVM_GETBKCOLOR clrBk:FFFFFFFF
 <12> 000100AE S LVM_GETTEXTBKCOLOR
 <13> 000100AE R LVM_GETTEXTBKCOLOR clrText:00778895
 <14> 000100AE S LVM_GETTEXTCOLOR
 <15> 000100AE R LVM_GETTEXTCOLOR clrText:00000000
 <16> 000100AE S WM_SETTINGCHANGE wFlag:SPI_SETDESKWALLPAPER
 pszMetrics:0007F81C
 <17> 000100AE R WM_SETTINGCHANGE
 <18> 000100AE S WM_SETTINGCHANGE wFlag:SPI_SETDESKWALLPAPER
 pszMetrics:0007FB90
 <19> 000100AE R WM_SETTINGCHANGE
 }}}

 Not that that is much help. On a higher level, Wallpaper Master does use a
 single file for the wallpaper, and when it's time to change, it flushes
 new image data to the file, and triggers the WM_SETTINGCHANGE msg with the
 wFlag to notify the system. The display properties dialog just writes the
 new image path to "HKCU\!ControlPanel\Desktop\Wallpaper" and triggers a
 WM_SETTINGCHANGE msg with null params.

 Of course, there may be other subtle differences that I missed.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7317#comment:10>
Pidgin <http://pidgin.im>
Pidgin