GNOME Bugzilla – Bug 550559
v0.14.3 crashes when using zoom to fit
Last modified: 2011-03-07 10:55:08 UTC
Steps to reproduce: 1. Create 2 tasks 2. Links the tasks 3. Set the duration so that the tasks do not fit on the screen anymore 4. Use Zoom to Fit Stack trace: Other information:
I do not get a stack trace, but I reproduced the bug by starting planner from the terminal. I then get following error: ** (planner:2521): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' failed
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I can't reopen the bug, but I'm also having this problem. As soon as I press to 'zoom to fit' button, the program keeps hanging in an endless loop while the message '** (planner:5947): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' failed' is being printed in the console. I took multiple stack traces as this appears to be and endless loop:
+ Trace 208882
== I think this endless loop is caused by the function gantt_header_expose_event in planner-gantt-header.c
Hey Erik, your stacktrace still misses debug symbols :( I'd like you to install up-to-date debug-packages as per comment #1. Would you also mind to run planner with the environment variable G_DEBUG set to "fatal_warnings" as per http://library.gnome.org/devel/glib/unstable/glib-running.html? It makes the application crash once the warning or critical message is raised. Thanks in advance.
$ G_DEBUG=fatal-criticals gdb /usr/bin/planner GNU gdb Fedora (6.8-29.fc10) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"... (gdb) r Starting program: /usr/bin/planner [Thread debugging using libthread_db enabled] warning: the debug information found in "/usr/lib/debug//lib64/libuuid.so.1.2.debug" does not match "/lib64/libuuid.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/lib64/libuuid.so.1.2.debug" does not match "/lib64/libuuid.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libcom_err.so.2.1.debug" does not match "/lib64/libcom_err.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/lib64/libcom_err.so.2.1.debug" does not match "/lib64/libcom_err.so.2" (CRC mismatch). [New Thread 0x7ffff7fb17f0 (LWP 28904)] ** CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' failed aborting... Program received signal SIGABRT, Aborted. 0x000000358e632f05 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Missing separate debuginfos, use: debuginfo-install avahi-0.6.22-12.fc10.x86_64 avahi-glib-0.6.22-12.fc10.x86_64 bug-buddy-2.24.2-1.fc10.x86_64 dbus-glib-0.76-3.fc10.x86_64 dbus-libs-1.2.4-2.fc10.x86_64 e2fsprogs-libs-1.41.4-1.fc10.x86_64 elfutils-libelf-0.140-1.fc10.x86_64 expat-2.0.1-5.x86_64 gamin-0.1.9-6.fc10.x86_64 gnome-keyring-2.24.1-1.fc10.x86_64 gtk-nodoka-engine-0.7.2-1.fc10.x86_64 gvfs-1.0.3-6.fc10.x86_64 keyutils-libs-1.2-3.fc9.x86_64 libX11-1.1.4-6.fc10.x86_64 libXau-1.0.4-1.fc10.x86_64 libXcomposite-0.4.0-5.fc10.x86_64 libXcursor-1.1.9-3.fc10.x86_64 libXdamage-1.1.1-4.fc9.x86_64 libXdmcp-1.0.2-6.fc10.x86_64 libXext-1.0.4-1.fc9.x86_64 libXfixes-4.0.3-4.fc10.x86_64 libXi-1.1.3-4.fc9.x86_64 libXinerama-1.0.3-2.fc10.x86_64 libXrandr-1.2.3-1.fc10.x86_64 libXrender-0.9.4-3.fc9.x86_64 libacl-2.2.47-3.fc10.x86_64 libattr-2.4.43-2.fc10.x86_64 libcanberra-0.10-3.fc10.x86_64 libcanberra-gtk2-0.10-3.fc10.x86_64 libcap-2.10-2.fc10.x86_64 libgcc-4.3.2-7.x86_64 libogg-1.1.3-9.fc9.x86_64 libpng-1.2.35-1.fc10.x86_64 libselinux-2.0.73-1.fc10.x86_64 libstdc++-4.3.2-7.x86_64 libtdb-1.1.1-27.fc10.x86_64 libtool-ltdl-1.5.26-4.fc10.x86_64 libvorbis-1.2.0-5.fc10.x86_64 libxcb-1.1.91-5.fc10.x86_64 pixman-0.12.0-2.fc10.x86_64 (gdb) bt
+ Trace 213291
main_window = (GtkWidget *) 0x950000 geometry = (gchar *) 0x0 context = <value optimized out> entries = {{long_name = 0x4711aa "geometry", short_name = 103 'g', flags = 0, arg = G_OPTION_ARG_STRING, arg_data = 0x7fffffffe238, description = 0x471250 "Create the initial window with the given geometry.", arg_description = 0x4711b3 "GEOMETRY"}, {long_name = 0x0, short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x0, description = 0x0, arg_description = 0x0}} filename = <value optimized out> (gdb) This is with Fedora 10 with all the debug packages installed (the messages about '<value optimized out>' are caused by the compiler optimalisation flags used by Fedora)
Reopening as we have a good stacktrace. Thanks Erik :) I am also confirming this bug. Simply click "Tasks" in the left menu, "Insert Task" and give it a name and a duration of, say, 1000d. Switch to "Gantt" mode, click "zoom to fit". It'll then eat all the CPU and print CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' failed all the time. This happens on F10s 0.14.3. I can't build trunk so I can't say whether it happens on trunk.
Also happens on Fedora 11 (no surprise since planner version is the same as it was on F10 -- 0.14.3). This is a bug too serious to be 1 year old... :-( (it can result in loss of data if "zoom to fit" is tried on a file with lots of unsaved data)
Additional info: if the gantt chart is smaller than the screen area the operation works as expected -- the chart is expanded to take advantage of the extra space available. The problem occurs only when the chart needs to be shrunk.
Created attachment 147960 [details] [review] this makes it go away Following the same pattern for zoom in and zoom out makes the problem "go away"
This was a problem introduced in 0.14.3 by the patch that added dragging of task duration beyond the window size. I reimplemented said functionality in a better way, thereby fixing the zoom-to-fit crash. The fix will be in the next release. Thanks for reporting this.
Nice :-) What's with the patch attached then? Have you used it? Could you then set the status to committed? If not probably rejected. Anyway, which revision fixed this bug? (Maybe distros want to backport, you'll never know...)
Comment on attachment 147960 [details] [review] this makes it go away Maurice solved it another way.
(In reply to comment #11) > Nice :-) > What's with the patch attached then? Have you used it? Could you then set the > status to committed? If not probably rejected. Done. > Anyway, which revision fixed this bug? (Maybe distros want to backport, you'll > never know...) Fixed by 8e4fab5a5585e3e33b402c348ab3b5958eab8a8c.
*** Bug 610333 has been marked as a duplicate of this bug. ***
*** Bug 632546 has been marked as a duplicate of this bug. ***
*** Bug 636195 has been marked as a duplicate of this bug. ***
*** Bug 644061 has been marked as a duplicate of this bug. ***