After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 627609 - imapx user_flags memory leak in imapx_untagged()
imapx user_flags memory leak in imapx_untagged()
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 627707
 
 
Reported: 2010-08-21 23:19 UTC by David Woodhouse
Modified: 2013-09-14 16:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2010-08-21 23:19:35 UTC 
==30229== 220 bytes in 8 blocks are definitely lost in loss record 15,376 of 18,830
==30229==    at 0x4A0515D: malloc (vg_replace_malloc.c:195)
==30229==    by 0x3A4DC45784: g_malloc (in /lib64/libglib-2.0.so.0.2512.0)
==30229==    by 0x6695BBD: camel_flag_set (camel-folder-summary.c:4112)
==30229==    by 0x19DF66D6: imapx_parse_flags (camel-imapx-utils.c:108)
==30229==    by 0x19DF6CA6: imapx_parse_fetch (camel-imapx-utils.c:1465)
==30229==    by 0x19DFF394: imapx_untagged (camel-imapx-server.c:1343)
==30229==    by 0x19E05C0A: imapx_step (camel-imapx-server.c:1915)
==30229==    by 0x19E06FEA: parse_contents (camel-imapx-server.c:4565)
==30229==    by 0x19E0741A: imapx_parser_thread (camel-imapx-server.c:4632)
==30229==    by 0x3A4DC65DE3: ??? (in /lib64/libglib-2.0.so.0.2512.0)
Comment 1 Chenthill P 2010-08-30 12:19:58 UTC 
commit id - 00e24150751ae15fa9ad13631ac02eaa0126712e .
Comment 2 David Woodhouse 2010-09-03 00:36:09 UTC 
Still seeing it.

==21464== 196 bytes in 7 blocks are definitely lost in loss record 27,247 of 33,527
==21464==    at 0x4A0615D: malloc (vg_replace_malloc.c:195)
==21464==    by 0x3D3D645C80: g_malloc (gmem.c:134)
==21464==    by 0x68E4C2D: camel_flag_set (camel-folder-summary.c:4112)
==21464==    by 0x1A25B9A2: imapx_parse_flags (camel-imapx-utils.c:107)
==21464==    by 0x1A25BDD6: imapx_parse_fetch (camel-imapx-utils.c:1467)
==21464==    by 0x1A264514: imapx_untagged (camel-imapx-server.c:1343)
==21464==    by 0x1A26AE0A: imapx_step (camel-imapx-server.c:1926)
==21464==    by 0x1A26C1EA: parse_contents (camel-imapx-server.c:4578)
==21464==    by 0x1A26C61A: imapx_parser_thread (camel-imapx-server.c:4645)
==21464==    by 0x3D3D666745: g_thread_create_proxy (gthread.c:1897)
==21464==    by 0x359B007760: start_thread (pthread_create.c:301)
==21464==    by 0x359A8E14EC: clone (clone.S:115)
Comment 3 Milan Crha 2010-09-06 14:17:01 UTC 
I do not see this, could you find what flag is it, please?

I suspect it being related to camel-imapx-server.c:1414, which is:
> 1410	      /* This (UID + FLAGS for previously unknown message) might
> 1411	         happen during a SELECT (QRESYNC). We should use it. */
> 1412	      c(printf("flags changed for unknown uid %s\n.", uid));
> 1413	   }
> 1414	   finfo->user_flags = NULL;
> 1415	}
> 1416
> 1417	if (changed) {
Comment 4 Fabio Durán Verdugo 2010-11-14 03:17:17 UTC 
any news for this report?
Comment 5 Fabio Durán Verdugo 2011-01-03 01:59:08 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!