Bug 594318 – Crash at gdata-service.c:1040

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 594318 - Crash at gdata-service.c:1040


Summary:	Crash at gdata-service.c:1040


Status:	RESOLVED DUPLICATE of bug 589265

Product:	libgdata
Classification:	Platform
Component:	General
Version:	0.4.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	libgdata-maint
QA Contact:	libgdata-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-09-06 16:09 UTC by Priit Laes (IRC: plaes)
Modified:	2009-09-12 16:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description Priit Laes (IRC: plaes) 2009-09-06 16:09:23 UTC

Version: 2.27.2

What were you doing when the application crashed?
Started youtube search,
* Changed search string
* Pressed Cancel
* Started another search
CRASH :)

PS. Seems like "Find" and "Cancel" aren't marked for l10n?


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.26.3 2009-07-12 (Gentoo)
BugBuddy Version: 2.26.0

System: Linux 2.6.31-rc5-00470-g85dfd81 #166 SMP Tue Aug 11 13:36:25 EEST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Compact
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 398893056 vsize: 398893056 resident: 28905472 share: 15790080 rss: 28905472 rss_rlim: 18446744073709551615
CPU usage: start_time: 1252253046 rtime: 86 utime: 79 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f83d4dd8730 (LWP 17228)]
[New Thread 0x7f83bdf61910 (LWP 17684)]
[New Thread 0x7f83beb6c910 (LWP 17575)]
[New Thread 0x7f83c2c38910 (LWP 17260)]
0x00007f83d0438426 in __poll (fds=0x20ecb40, nfds=11, timeout=116) at ../sysdeps/unix/sysv/linux/poll.c:87
	in ../sysdeps/unix/sysv/linux/poll.c

+ Trace 217366

Thread 3 (Thread 0x7f83beb6c910 (LWP 17575))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 IA__g_spawn_sync
at gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at gspawn.c line 700
#3 bugbuddy_segv_handle
at gnome-breakpad.cc line 369
#4 <signal handler called>
#5 gdata_service_query
at gdata-service.c line 1040
#6 query_thread
at gdata-service.c line 860
#7 run_in_thread
at gsimpleasyncresult.c line 678
#8 io_job_thread
at gioscheduler.c line 182
#9 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#10 g_thread_create_proxy
at gthread.c line 635
#11 start_thread
at pthread_create.c line 297
#12 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
#13 ??

Comment 1 Philip Withnall 2009-09-12 15:41:31 UTC

What version of libgdata do you have installed? Could you please recompile it with debugging symbols?

"Find" and "Cancel" are both stock GTK+ buttons, so should be localisable there.

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Philip Withnall 2009-09-12 15:53:38 UTC

(In reply to comment #1)
> What version of libgdata do you have installed? Could you please recompile it
> with debugging symbols?

Argh. Ignore the debug symbol request. I haven't yet got the hang of the new Bugzilla. I'll take a look at this in a bit.

Comment 3 Philip Withnall 2009-09-12 16:00:52 UTC

It's actually a dupe of bug #589265. I'll try to find some time to backport the fix to the 0.4 branch (along with some others), and make a minor release to coincide with GNOME 2.28. Thanks.

*** This bug has been marked as a duplicate of bug 589265 ***