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 577640 - Crashes using GAsyncQueue
Crashes using GAsyncQueue
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
: 580612 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-01 19:37 UTC by Snark
Modified: 2009-05-16 08:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Valgrind output (compressed) (7.01 KB, application/x-compressed-tar)
2009-05-09 16:07 UTC, Eugen Dedu 		Details
gdb output, thread 4 is the important one, I think (17.50 KB, text/plain)
2009-05-09 16:08 UTC, Eugen Dedu 		Details

Description Snark 2009-04-01 19:37:19 UTC 
I have a nice bug #570008, where two crashes are described -- let's fork the reports ; this one is about a crash using GAsyncQueue, and I think I should push it to glib (still reporting against ekiga first since that's where it comes from) :

+ Trace 214098

  • #0 malloc_consolidate
    at malloc.c line 4889
  • #1 _int_malloc
    at malloc.c line 4229
  • #2 __libc_calloc
    at malloc.c line 3946
  • #3 IA__g_malloc0
    at /tmp/buildd/glib2.0-2.20.0/glib/gmem.c line 151
  • #4 IA__g_slice_alloc
    at /tmp/buildd/glib2.0-2.20.0/glib/gslice.c line 444
  • #5 IA__g_list_prepend
    at /tmp/buildd/glib2.0-2.20.0/glib/glist.c line 169
  • #6 IA__g_queue_push_head
    at /tmp/buildd/glib2.0-2.20.0/glib/gqueue.c line 295
  • #7 IA__g_async_queue_push_unlocked
    at /tmp/buildd/glib2.0-2.20.0/glib/gasyncqueue.c line 245
  • #8 IA__g_async_queue_push
    at /tmp/buildd/glib2.0-2.20.0/glib/gasyncqueue.c line 226 






Comment 1


Eugen Dedu





          2009-04-15 16:02:34 UTC
        



Any news about this crash?






Comment 2


Snark





          2009-04-28 16:23:52 UTC
        



*** Bug 580612 has been marked as a duplicate of this bug. ***






Comment 3


Eugen Dedu





          2009-05-09 11:15:40 UTC
        



Could someone from glib look at this bug please?  It has been hitting ekiga since January/February and is the main blocker for a stable release of ekiga.






Comment 4


Matthias Clasen





          2009-05-09 13:33:56 UTC
        



The stacktrace in the description is a crash inside malloc, so I'd say you have memory corruption somewhere. Now, this could still be caused by glib, certainly.
But I don't see any strong hints that would allow me to look for something.






Comment 5


Matthias Clasen





          2009-05-09 13:34:44 UTC
        



I would recommend valgrind to get a grip on the cause of the memory corruption.






Comment 6


Eugen Dedu





          2009-05-09 16:07:13 UTC
        



Created attachment 134312 [details]
Valgrind output (compressed)

I start ekiga again, once with valgrind, once with gdb.  Here are the outputs.






Comment 7


Eugen Dedu





          2009-05-09 16:08:26 UTC
        



Created attachment 134313 [details]
gdb output, thread 4 is the important one, I think






Comment 8


Matthias Clasen





          2009-05-09 16:29:35 UTC
        



Looks indeed like memory corruption.

Moving back to ekiga for now.






Comment 9


Eugen Dedu





          2009-05-16 08:32:47 UTC
        



It was indeed a problem in ekiga, thanks Matthias!  Julien has just fixed it.