shotwell crashed with SIGSEGV in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_insert_unique_()

Bug #850549 reported by Ian Nicholson on 2011-09-15
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Shotwell
New
Undecided
Unassigned
gexiv2
New
Undecided
Unassigned
shotwell (Ubuntu)
Low
Unassigned

Bug Description

Occurred when I used the "send to" option in the right click menu

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: shotwell 0.11.1-0ubuntu1 [modified: usr/share/glib-2.0/schemas/gschemas.compiled]
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 14 20:35:22 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: shotwell
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f61176109f9 <_ZNSt8_Rb_treeISsSt4pairIKSsSsESt10_Select1stIS2_ESt4lessISsESaIS2_EE17_M_insert_unique_ESt23_Rb_tree_const_iteratorIS2_ERKS2_+393>: mov -0x18(%rsi),%r8
 PC (0x7f61176109f9) ok
 source "-0x18(%rsi)" (0xfffffffffffffff7) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_insert_unique_(std::_Rb_tree_const_iterator<std::pair<std::string const, std::string> >, std::pair<std::string const, std::string> const&) () from /usr/lib/libexiv2.so.10
 ?? () from /usr/lib/libexiv2.so.10
 ?? () from /usr/lib/libexiv2.so.10
 ?? () from /usr/lib/libexiv2.so.10
 ?? () from /usr/lib/libexiv2.so.10
Title: shotwell crashed with SIGSEGV in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_insert_unique_()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Ian Nicholson (imnichol) wrote :
visibility: private → public

StacktraceTop:
 size (this=0x7f60fc186f58) at /usr/include/c++/4.5/bits/basic_string.h:702
 compare (__str=..., this=0x7f60fc186f58) at /usr/include/c++/4.5/bits/basic_string.h:2132
 operator< <char, std::char_traits<char>, std::allocator<char> > (__rhs=..., __lhs=...) at /usr/include/c++/4.5/bits/basic_string.h:2419
 operator() (__y=..., __x=..., this=<optimized out>) at /usr/include/c++/4.5/bits/stl_function.h:230
 std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_insert_unique_ (this=0x7f60fc186f30, __position=..., __v=...) at /usr/include/c++/4.5/bits/stl_tree.h:1240

Changed in shotwell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jim Nelson (yorba-jim) wrote :

This is ticketed upstream at http://redmine.yorba.org/issues/4120

Jim Nelson (yorba-jim) wrote :

This appears to be a threading issue when initializing Exiv2. This also bit digiKam a while back: http://bugs.kde.org/show_bug.cgi?id=166424

I'll continue looking into this problem.

Changed in shotwell (Ubuntu):
status: New → Triaged
importance: Medium → Low
tags: added: precise
Lucas Beeler (lucas-yorba) wrote :

This issue has been fixed upstream and the fix is present in Shotwell 0.12.x as ships with Precise.

Changed in shotwell (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
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.