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 308544 - crash when text editor open a big file
crash when text editor open a big file
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
2.10.x
Other other
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-21 16:44 UTC by antonio
Modified: 2005-08-24 14:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description antonio 2005-06-21 16:44:12 UTC 
Distribution: Debian 3.1
Package: gnome-panel
Severity: critical
Version: GNOME2.10.0 2.10.x
Gnome-Distributor: Ubuntu
Synopsis: crash when text editor open a big file
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock applet
Bugzilla-Version: 2.10.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1221836064 (LWP 7434)]
[New Thread -1224447056 (LWP 7468)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 61353

Thread 2 (Thread -1224447056 (LWP 7468))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-21 16:44 UTC -------
Comment 1 Vincent Untz 2005-08-24 14:04:13 UTC 
Most probably fixed with:

2005-05-02  Mark McLoughlin  <mark@skynet.ie>
	
	Change things around so that we don't 1) slave the lifecycle
	of the EggRecentViewGtk to the menu it manages, 2) incorrectly
	unref the menu after creating the view and 3) take a ref on
	the menu in EggRecentViewgtk.

	* panel-recent.[ch]: (panel_recent_append_documents_menu):
	Re-work so that it returns the newly created EggRecentViewGtk
	and allows it to be re-used by passing it back in as a parameter.
	
	* panel-menu-items.c:
	(panel_place_menu_item_create_menu): hold a ref on the
	EggRecentViewGtk and re-user when re-creating the menu.
	(panel_place_menu_item_finalize): unref the view.
	
	* egg-recent-view-gtk.c:
	(egg_recent_view_gtk_clear),
	(egg_recent_view_gtk_set_list): don't barf if view->menu is NULL.
	(egg_recent_view_gtk_finalize): don't unref the menu.
	(egg_recent_view_gtk_set_menu): don't take a ref on the menu.
	There's no point in us updating a menu which has been destroye