fusesmb.cache crashed with SIGSEGV in talloc_free()

Bug #279526 reported by Robert Jordens
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fusesmb (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: fusesmb

when running fusesmb on a medium busy network, fusesmb.cache crashes about once a day (but gets restarted again).

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/fusesmb.cache
Package: fusesmb 0.8.7-1
ProcAttrCurrent: unconfined
ProcCmdline: fusesmb.cache
Signal: 11
SourcePackage: fusesmb
StacktraceTop:
 talloc_free () from /usr/lib/libtalloc.so.1
 ?? () from /usr/lib/libsmbclient.so.0
 talloc_free () from /usr/lib/libtalloc.so.1
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
Title: fusesmb.cache crashed with SIGSEGV in talloc_free()
Uname: Linux 2.6.27-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin plugdev thinkfinger vboxusers video

Tags: apport-crash
Revision history for this message
Robert Jordens (jordens) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:talloc_free () from /usr/lib/libtalloc.so.1
talloc_pop () from /usr/lib/libsmbclient.so.0
talloc_free () from /usr/lib/libtalloc.so.1
internal_resolve_name () from /usr/lib/libsmbclient.so.0
resolve_name () from /usr/lib/libsmbclient.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in fusesmb:
importance: Undecided → Medium
Revision history for this message
Léa GRIS (lea-gris) wrote :

Crashed here with same cause but no significant network load.

Revision history for this message
Forest (foresto) wrote :

Could this be related to bug 198351 and bug 293233?

Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in fusesmb (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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