evolution-data-server-2.22 crashed with signal 5 in IA__g_realloc()

Changed Security from Private to Public

root@2HewittRand-desktop:~# apport-retrace /var/crash/_usr_lib_evolution_evolution-data-server-2.22.0.crash
WARNING: package libsepol1-dbgsym not available
WARNING: package libselinux1-dbgsym not available
WARNING: package libgcc1-dbgsym not available
WARNING: package sed-dbgsym not available
WARNING: package libgnomevfs2-0-dbgsym not available
WARNING: package libpam-modules-dbgsym not available
WARNING: package gcc-4.2-base-dbgsym not available
WARNING: package libpam0g-dbgsym not available
WARNING: package libavahi-common-data-dbgsym not available
WARNING: package libaudiofile0-dbgsym not available
WARNING: package libbz2-1.0-dbgsym not available
WARNING: package libdb4.6-dbgsym not available
WARNING: package libxml2-dbgsym not available
WARNING: package python2.5-dbgsym not available
WARNING: package debianutils-dbgsym not available
WARNING: package perl-base-dbgsym not available
Extracting templates from packages: 100%
(Reading database ... 136174 files and directories currently installed.)
Removing libnspr4-0d-dbg ...
Selecting previously deselected package consolekit-dbgsym.
(Reading database ... 136169 files and directories currently installed.)
Unpacking consolekit-dbgsym (from .../consolekit-dbgsym_0.2.3-3ubuntu3_i386.ddeb) ...
Selecting previously deselected package coreutils-dbgsym.
Unpacking coreutils-dbgsym (from .../coreutils-dbgsym_6.10-3ubuntu1_i386.ddeb) ...
Selecting previously deselected package dbus-dbgsym.
Unpacking dbus-dbgsym (from .../dbus-dbgsym_1.1.2-1ubuntu2_i386.ddeb) ...
Selecting previously deselected package dpkg-dbgsym.
Unpacking dpkg-dbgsym (from .../dpkg-dbgsym_1.14.15ubuntu1_i386.ddeb) ...
Selecting previously deselected package evolution-data-server-dbgsym.
Unpacking evolution-data-server-dbgsym (from .../evolution-data-server-dbgsym_2.21.90-0ubuntu2_i386.ddeb) ...
Selecting previously deselected package gamin-dbgsym.
Unpacking gamin-dbgsym (from .../gamin-dbgsym_0.1.9-2ubuntu2_i386.ddeb) ...
Selecting previously deselected package gconf2-dbgsym.
Unpacking gconf2-dbgsym (from .../gconf2-dbgsym_2.21.90-0ubuntu1_i386.ddeb) ...
Selecting previously deselected package libacl1-dbgsym.
Unpacking libacl1-dbgsym (from .../libacl1-dbgsym_2.2.45-1_i386.ddeb) ...
Selecting previously deselected package libasound2-dbgsym.
Unpacking libasound2-dbgsym (from .../libasound2-dbgsym_1.0.15-3ubuntu3_i386.ddeb) ...
Selecting previously deselected package libattr1-dbgsym.
Unpacking libattr1-dbgsym (from .../libattr1-dbgsym_1%3a2.4.39-1_i386.ddeb) ...
Selecting previously deselected package libavahi-client3-dbgsym.
Unpacking libavahi-client3-dbgsym (from .../libavahi-client3-dbgsym_0.6.22-2ubuntu1_i386.ddeb) ...
Selecting previously deselected package libavahi-common3-dbgsym.
Unpacking libavahi-common3-dbgsym (from .../libavahi-common3-dbgsym_0.6.22-2ubuntu1_i386.ddeb) ...
Selecting previously deselected package libavahi-glib1-dbgsym.
Unpacking libavahi-glib1-dbgsym (from .../libavahi-glib1-dbgsym_0.6.22-2ubuntu1_i386.ddeb) ...
Selecting previously deselected package libbonobo2-0-dbgsym.
Unpacking libbonobo2-0-dbgsym (from .../libbonobo2-0-dbgsym_2.21.90-1_i386.ddeb) ...
Selecting previously deselected package libcamel1.2-11-db...

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

root@2HewittRand-desktop:~# sudo apt-get install valgrind
Reading package lists... Done
Building dependency tree
Reading state information... Done
valgrind is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@2HewittRand-desktop:~# G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log evolution-data-server
valgrind: evolution-data-server: command not found

root@2HewittRand-desktop:~# G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/evolution/evolution-data-server-2.22
evolution-data-server-Message: Starting server
e-data-server-Message: adding type `EBookBackendLDAPFactory'
e-data-server-Message: adding type `EBookBackendFileFactory'
e-data-server-Message: adding type `EBookBackendGroupwiseFactory'
e-data-server-Message: adding type `ECalBackendGoogleTodosFactory'
e-data-server-Message: adding type `ECalBackendGoogleEventsFactory'
e-data-server-Message: adding type `ECalBackendGroupwiseTodosFactory'
e-data-server-Message: adding type `ECalBackendGroupwiseEventsFactory'
e-data-server-Message: adding type `ECalBackendGroupwiseJournalFactory'
e-data-server-Message: adding type `EBookBackendVCFFactory'
e-data-server-Message: adding type `ECalBackendContactsEventsFactory'
e-data-server-Message: adding type `ECalBackendCalDAVEventsFactory'
e-data-server-Message: adding type `ECalBackendHttpTodosFactory'
e-data-server-Message: adding type `ECalBackendHttpEventsFactory'
e-data-server-Message: adding type `ECalBackendHttpMemosFactory'
e-data-server-Message: adding type `ECalBackendFileTodosFactory'
e-data-server-Message: adding type `ECalBackendFileEventsFactory'
e-data-server-Message: adding type `ECalBackendFileJournalFactory'
e-data-server-Message: adding type `ECalBackendWeatherEventsFactory'
libedata-book-Message: Error registering the PAS factory: already active

(evolution-data-server-2.22:6841): evolution-data-server-WARNING **: server.c:392: could not initialize Server service "BOOKS"; terminating
root@2HewittRand-desktop:~#

Added Info

root@2HewittRand-desktop:~# tar -zcf valgrind-logs-/usr/lib/evolution/evolution-data-server-2.22.tar.gz valgrind.log.*
tar: valgrind-logs-/usr/lib/evolution/evolution-data-server-2.22.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: valgrind.log.*: Cannot stat: No such file or directory
root@2HewittRand-desktop:~#

you didn't add any useful information there

StacktraceTop:IA__g_realloc (mem=0x0, n_bytes=1073741824)
g_ptr_array_maybe_expand (array=0x8082100,
IA__g_ptr_array_add (farray=0x8082100, data=0x8090c28)
e_memchunk_alloc (m=0x8086df8) at e-memory.c:164
e_memchunk_alloc0 (m=0x8086df8) at e-memory.c:177

sorry , that was not my intent, I tried to post a valgrind report as requested.
I don't know enough about the process to know if that info is helpful or not.
I'm not even sure I did the command right.
It helps when people post the command(s) they would like us to try.
I did go to the weblink and try to follow the form, but sometimes I don't know enough of what's happening to enter it right to get output that would be helpful. Thanks.

I guess maybe I don't understand, a part or two of this process relating to an Incomplete Status.
If a bug/crash report gets marked as Incomplete Status, are we suppose to try to change the status; if we add info-hopefully useful but maybe not ?
maybe from Incomplete to New-? for example. Should there be another choice like (responded, answered, commented, question, help), or will it just get noticed if we add a comment and don't change the status ?

Remember, this bug report is a duplicate. Comment here only if you think the duplicate status is wrong.
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/179217
evolution-data-server-2.22 crashed with signal 5 in g_realloc()
I don't know if this status is right or wrong.
evolution-data-server-2.22 crashed with signal 5 in IA__g_realloc()
the error message is slightly different. In looking at the other bug which I also got it seems little different.

You can change the bug to NEW if you add requested informations, you didn't attach the logs on this bug though

Hello miked,

This bug is already assigned to the desktop-bugs group. All of us that belong to this group will be emailed on all updates to it.

Incomplete means that we are still missing some information/data that we consider necessary to fully identify the issue (and, as a result, move the bug to some other status). In your case, this bug clearly looks like a dup of bug 179217, so it was marked as such. Until otherwise shown, you should use the original bug 179217 for all your comments (even the above). A valgrind report would certainly help us -- mostly one that goes up to the actual crash. By the way, please upload the valgrind report to bug 179217, not this one.

Re. your previous remark: just upload the valgrind report, no need to create a tarball. Launchpad should be able to easily manage large files. Your 'tar' failed because the tarball (the archive) you were trying to create had slashes in the name: "valgrind-logs-/usr/lib/evolution/evolution-data-server-2.22.tar.gz". So the shell interpreted it as being subdirectories under you current directory: it went looking for a directory called "valgrind-logs-", under it another directory called "usr", under it another one called "lib", etc, etc.

Your valgrind command was correct (the second time you ran it), so it will have -- hopefully -- a clear indication of where the error is.

It seems to be that you get the error every time; if this is the case, this is also interesting on and by itself, since the original reporter of bug 179217 did not indicate this was the case.

On the difficulties you had: can you expand a bit more on what was missing/incomplete/unexplained? We do try to explain it, but we are hampered by our own bias: something may be so simple (for some of us), that it is deemed as not needing explanations. Of course, as you point out, a bad move... if we know where we mis-explained, we can redo/expand it.

Finally, on when to change the status from incomplete: usually this will be done by someone with QA access. See [1] below for the formal definition of the bug stati. [2] should be a good reference to the work done by the bugsquad.

[1] https://wiki.ubuntu.com/Bugs/Status?highlight=%28CategoryBugSquad%29
[2] https://wiki.ubuntu.com/BugSquad/KnowledgeBase