GNOME Bugzilla – Bug 653736
Crash due to out of memory from google backend
Last modified: 2011-08-16 02:06:57 UTC
Created attachment 191006 [details] valgrind log Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=714418 abrt version: 2.0.1 architecture: x86_64 cmdline: /usr/libexec/e-addressbook-factory comment: Openning the addressbook. component: evolution-data-server crash_function: _int_realloc executable: /usr/libexec/e-addressbook-factory kernel: 2.6.38.8-32.fc15.x86_64 os_release: Fedora release 15 (Lovelock) package: evolution-data-server-3.0.2-1.fc15 rating: 4 reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
+ Trace 227626
Thread 1 (Thread 0x7fc1109797e0 (LWP 1622))
After more investigation from the reporter (he provided the above attached valgrind log), it seems that google addressbook backend is leaking memory. Mine comment on the downstream bug: The valgrind log shows some definitely lost memory, mostly related to google backend/account, but still, it may not result in a low memory for the process: > LEAK SUMMARY: > definitely lost: 88 bytes in 17 blocks > indirectly lost: 192 bytes in 1 blocks > possibly lost: 10,524 bytes in 194 blocks > still reachable: 1,614,257 bytes in 7,707 blocks On the other hand, having e-addressbook-factory running for a longer time, with some extensive using of a google backend, I believe it can get out of memory too. There are also interesting these runtime warnings: > ...libebookbackendgoogle-WARNING **: Connection to Google already established. > ...g_object_unref: assertion `G_IS_OBJECT (object)' failed > ...g_object_unref: assertion `G_IS_OBJECT (object)' failed > > ...libebookbackendgoogle-WARNING **: Connection to Google already established. > ...g_object_unref: assertion `G_IS_OBJECT (object)' failed > ...g_object_unref: assertion `G_IS_OBJECT (object)' failed
That valgrind log isn't very useful without debug symbols for the Google Contacts backend and libgdata. Would it be possible to get a new one with debug symbol packages installed? The same is true for the assertion failures: I can't do much without backtraces. :-( Thanks.
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!