Bug 626151 – Crash in miUnionNonO, e_day_view_layout_timeout_cb at e-day-view.c line 8451

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 626151 - Crash in miUnionNonO, e_day_view_layout_timeout_cb at e-day-view.c line 8451


Summary:	Crash in miUnionNonO, e_day_view_layout_timeout_cb at e-day-view.c line 8451


Status:	RESOLVED DUPLICATE of bug 621688

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.32.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-08-05 22:30 UTC by David Ronis
Modified:	2013-09-13 01:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.31/2.32

Description David Ronis 2010-08-05 22:30:41 UTC

Version: 2.32.x

What were you doing when the application crashed?
Evolution had been up and stable all day.  I'd switched to my calendar,
which was set to "work week" display.  I pressed the -> to go to next week and here we are.



Distribution: Slackware Slackware 12.2.0
Gnome Release: 2.31.6 2010-08-04 (GARNOME)
BugBuddy Version: 2.31.3

System: Linux 2.6.34-rc5-ge520683 #2 SMP PREEMPT Tue Jun 8 13:13:01 EDT 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10899000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Default
Icon Theme: gnome
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 287797248 vsize: 287797248 resident: 110469120 share: 29724672 rss: 110469120 rss_rlim: 18446744073709551615
CPU usage: start_time: 1281033519 rtime: 10687 utime: 7123 stime: 3564 cutime:63 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome-svn-2.90/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb08efb90 (LWP 3524)]
[New Thread 0xa904ab90 (LWP 25754)]
[New Thread 0xaeeffb90 (LWP 23138)]
[New Thread 0xaf6ffb90 (LWP 23137)]
[New Thread 0xb1227b90 (LWP 23130)]
[New Thread 0xb54d1b90 (LWP 23129)]
0xb5db2171 in waitpid () from /lib/libpthread.so.0

+ Trace 223128

Thread 1 (Thread 0xb5a4cb30 (LWP 23121))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
at gspawn.c line 385
#2 g_spawn_command_line_sync
at gspawn.c line 699
#3 run_bug_buddy
at gnome-segvhanlder.c line 240
#4 bugbuddy_segv_handle
at gnome-segvhanlder.c line 191
#5 <signal handler called>
#6 raise
from /lib/libc.so.6
#7 abort
from /lib/libc.so.6
#8 g_assertion_message
at gtestutils.c line 1358
#9 g_assertion_message_expr
at gtestutils.c line 1369
#10 miUnionNonO
at gdkregion-generic.c line 1114
#11 miRegionOp
at gdkregion-generic.c line 1021
#12 IA__gdk_region_union
at gdkregion-generic.c line 1266
#13 impl_window_add_update_area
at gdkwindow.c line 5736
#14 gdk_window_invalidate_maybe_recurse_full
at gdkwindow.c line 5847
#15 gdk_window_invalidate_maybe_recurse_full
at gdkwindow.c line 5812
#16 gdk_window_invalidate_region_full
at gdkwindow.c line 5902
#17 gdk_window_invalidate_rect_full
at gdkwindow.c line 5684
#18 IA__gtk_widget_queue_draw_area
at gtkwidget.c line 3671
#19 IA__gtk_widget_queue_draw
at gtkwidget.c line 3741
#20 e_day_view_layout_timeout_cb
at e-day-view.c line 8451
#21 g_timeout_dispatch
at gmain.c line 3555
#22 g_main_dispatch
at gmain.c line 2119
#23 g_main_context_dispatch
at gmain.c line 2672
#24 g_main_context_iterate
at gmain.c line 2750
#25 g_main_loop_run
at gmain.c line 2958
#26 IA__gtk_main
at gtkmain.c line 1237
#27 main
at main.c line 646


	Inferior 1 [process 23121] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]

Comment 1 Akhil Laddha 2010-08-06 06:35:07 UTC

possible dupe of bug 621688

Comment 2 Milan Crha 2010-09-10 07:12:28 UTC

I tried to reproduce this with actual master, by moving forth and back in a week view, but even it crashed for me when I clicked "Today", then I didn't get a backtrace, so I do not know whether it is the same issue as this or not, and I'm not able to reproduce it under gdb again, unfortunately.

(In reply to comment #1)
> possible dupe of bug 621688

Might be true, same crash function and top of the backtrace, so it seems like another way to reproduce this.

Comment 3 Milan Crha 2010-10-21 10:28:16 UTC


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