Bug 995699

Summary: [abrt] recoll-1.19.4-2.fc18: 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> > ...
Product: [Fedora] Fedora Reporter: michelenani
Component: recollAssignee: Terje Røsten <terje.rosten>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:da6952ca07a4135f829021dabb4409661d920e95
Fixed In Version: recoll-1.19.9-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-23 19:43:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description michelenani 2013-08-10 08:13:33 UTC
Description of problem:
While re-starting, after a huge updating of my Fedora18

Version-Release number of selected component:
recoll-1.19.4-2.fc18

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/recollindex -w 60 -m
crash_function: 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_erase
executable:     /usr/bin/recollindex
kernel:         3.9.11-200.fc18.i686.PAE
runlevel:       N 5
uid:            1000
xsession_errors: :3:recollindex.cpp:371:recollindex: starting up

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 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_erase at /usr/include/c++/4.7.2/bits/stl_tree.h:1082
 #5 ~_Rb_tree at /usr/include/c++/4.7.2/bits/stl_tree.h:646
 #6 ~map at /usr/include/c++/4.7.2/bits/stl_map.h:90
 #7 ~pair at /usr/include/c++/4.7.2/bits/stl_pair.h:88
 #8 destroy at /usr/include/c++/4.7.2/ext/new_allocator.h:123
 #9 _M_destroy_node at /usr/include/c++/4.7.2/bits/stl_tree.h:394
 #10 std::_Rb_tree<std::string, std::pair<std::string const, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > >, std::_Select1st<std::pair<std::string const, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > > >, std::less<std::string>, std::allocator<std::pair<std::string const, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > > > >::_M_erase at /usr/include/c++/4.7.2/bits/stl_tree.h:1084
 #12 ~_Rb_tree at /usr/include/c++/4.7.2/bits/stl_tree.h:646
 #13 ~map at /usr/include/c++/4.7.2/bits/stl_map.h:90
 #14 ~ConfSimple at ../utils/conftree.h:143

Comment 1 michelenani 2013-08-10 08:13:38 UTC
Created attachment 785108 [details]
File: backtrace

Comment 2 michelenani 2013-08-10 08:13:41 UTC
Created attachment 785109 [details]
File: cgroup

Comment 3 michelenani 2013-08-10 08:13:44 UTC
Created attachment 785110 [details]
File: core_backtrace

Comment 4 michelenani 2013-08-10 08:13:47 UTC
Created attachment 785111 [details]
File: dso_list

Comment 5 michelenani 2013-08-10 08:13:50 UTC
Created attachment 785112 [details]
File: environ

Comment 6 michelenani 2013-08-10 08:13:53 UTC
Created attachment 785113 [details]
File: limits

Comment 7 michelenani 2013-08-10 08:13:56 UTC
Created attachment 785114 [details]
File: maps

Comment 8 michelenani 2013-08-10 08:13:59 UTC
Created attachment 785115 [details]
File: open_fds

Comment 9 michelenani 2013-08-10 08:14:02 UTC
Created attachment 785116 [details]
File: proc_pid_status

Comment 10 michelenani 2013-08-10 08:14:05 UTC
Created attachment 785118 [details]
File: var_log_messages

Comment 11 Terje Røsten 2013-08-19 18:37:29 UTC
Thanks for your report, are able to reproduce? 

Or was this just a single crash after update?

Comment 12 Fedora Update System 2013-11-05 22:12:59 UTC
recoll-1.19.8-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/recoll-1.19.8-1.fc19

Comment 13 Fedora Update System 2013-11-05 22:13:36 UTC
recoll-1.19.8-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/recoll-1.19.8-1.fc20

Comment 14 Fedora Update System 2013-11-05 22:14:05 UTC
recoll-1.19.8-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/recoll-1.19.8-1.fc18

Comment 15 Fedora Update System 2013-11-06 18:21:59 UTC
Package recoll-1.19.8-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing recoll-1.19.8-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20750/recoll-1.19.8-1.fc20
then log in and leave karma (feedback).

Comment 16 Fedora Update System 2013-11-23 19:43:45 UTC
recoll-1.19.9-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Fedora Update System 2013-11-23 19:44:48 UTC
recoll-1.19.9-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 18 Fedora Update System 2013-11-24 04:04:50 UTC
recoll-1.19.9-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.