maximus crashed with SIGSEGV in free()

Bug #347382 reported by diggiewiggie
166
This bug affects 33 people
Affects Status Importance Assigned to Milestone
Maximus
Fix Released
Critical
Jason Smith
maximus (Ubuntu)
Fix Released
High
Unassigned
Nominated for Jaunty by diggiewiggie

Bug Description

Binary package hint: maximus

Description: Ubuntu jaunty (development branch)
Release: 9.04

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/maximus
Package: maximus 0.4.8-0ubuntu1
ProcCmdline: maximus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: maximus
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 XFree () from /usr/lib/libX11.so.6
 ?? ()
 IA__g_cclosure_marshal_VOID__OBJECT (closure=0x8b8c168,
 IA__g_closure_invoke (closure=0x8b8c168, return_value=0x0,
Title: maximus crashed with SIGSEGV in free()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
diggiewiggie (widzspeed) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:*__GI___libc_free (mem=0xbfbe3024) at malloc.c:3614
XFree (data=0xbfbe3024) at ../../src/XlibInt.c:3049
on_window_opened (screen=0x8b1f530, window=0x8b915e8,
IA__g_cclosure_marshal_VOID__OBJECT (closure=0x8b8c168,
IA__g_closure_invoke (closure=0x8b8c168, return_value=0x0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in maximus:
importance: Undecided → Medium
visibility: private → public
Changed in maximus (Ubuntu):
status: New → Confirmed
Neil J. Patel (njpatel)
Changed in maximus:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 0.4.11
assignee: nobody → Jason Smith (jassmith)
milestone: 0.4.11 → none
Jason Smith (jassmith)
Changed in maximus:
milestone: none → ubuntu-9.10-ui-freeze
Revision history for this message
Jason Smith (jassmith) wrote :

I am fairly certain the robustness changes that went in the last patch will have fixed this issue.

Revision history for this message
Neil J. Patel (njpatel) wrote :

Marking as fix-committed as per Jasons last comment. Haven't come across this again since.

Changed in maximus:
status: Confirmed → Fix Committed
Neil J. Patel (njpatel)
Changed in maximus:
status: Fix Committed → Fix Released
Revision history for this message
Paul Larson (pwlars) wrote :

Neil or Jason, has this fix already been pushed into karmic?

Changed in maximus (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
Paul Larson (pwlars) wrote :

Ok, it looks like the robustness changes you were talking about happened in rev45, and we currently have 0.4.11 which was tagged in rev48, so I'm marking this fix released.

Changed in maximus (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.