Bug 980947

Summary: [abrt] recoll-1.19.4-2.fc18: inflate_table: Process /usr/bin/recoll was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Giuseppe Fiorentino <peppe.fiorentino>
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: jfd, terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a07efc22b6cb9ab4be7415e5e1bdce14282ed329
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:25 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: xsession_errors none

Description Giuseppe Fiorentino 2013-07-03 15:47:14 UTC
Version-Release number of selected component:
recoll-1.19.4-2.fc18

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        recoll
crash_function: inflate_table
executable:     /usr/bin/recoll
kernel:         3.9.6-200.fc18.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jul  3 16:46:24 localhost abrt[17103]: Saved core dump of pid 4007 (/usr/bin/recoll) to /var/tmp/abrt/ccpp-2013-07-03-16:46:19-4007 (1151696896 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 inflate_table at inftrees.c:238
 #1 inflate at inflate.c:925
 #2 ChertTable::read_tag at backends/chert/chert_table.cc:1258
 #3 ChertTable::get_exact_entry at backends/chert/chert_table.cc:1195
 #4 ChertRecordTable::get_record at backends/chert/chert_record.cc:48
 #5 ChertDocument::do_get_data at backends/chert/chert_document.cc:58
 #6 ValueStreamDocument::do_get_data at matcher/valuestreamdocument.cc:108
 #7 Xapian::Document::Internal::get_data at api/omdocument.cc:290
 #8 Xapian::Document::get_data at api/omdocument.cc:66
 #9 Rcl::QSorter::operator() at ../rcldb/rclquery.cpp:82

Comment 1 Giuseppe Fiorentino 2013-07-03 15:47:21 UTC
Created attachment 768302 [details]
File: backtrace

Comment 2 Giuseppe Fiorentino 2013-07-03 15:47:24 UTC
Created attachment 768303 [details]
File: cgroup

Comment 3 Giuseppe Fiorentino 2013-07-03 15:47:28 UTC
Created attachment 768304 [details]
File: core_backtrace

Comment 4 Giuseppe Fiorentino 2013-07-03 15:47:33 UTC
Created attachment 768305 [details]
File: dso_list

Comment 5 Giuseppe Fiorentino 2013-07-03 15:47:37 UTC
Created attachment 768306 [details]
File: environ

Comment 6 Giuseppe Fiorentino 2013-07-03 15:47:41 UTC
Created attachment 768307 [details]
File: limits

Comment 7 Giuseppe Fiorentino 2013-07-03 15:47:46 UTC
Created attachment 768308 [details]
File: maps

Comment 8 Giuseppe Fiorentino 2013-07-03 15:47:51 UTC
Created attachment 768310 [details]
File: open_fds

Comment 9 Giuseppe Fiorentino 2013-07-03 15:47:55 UTC
Created attachment 768311 [details]
File: proc_pid_status

Comment 10 Giuseppe Fiorentino 2013-07-03 15:47:58 UTC
Created attachment 768312 [details]
File: xsession_errors

Comment 11 Jean-Francois Dockes 2013-08-15 10:29:31 UTC
Hi, and thanks for reporting this. 

It seems that the crash was caused by initiating new activity (scrolling or exposing the result table might be enough) while a search was active. This is a bug of course, the GUI should protect against it, but it currently doesn't do it sufficiently. 

For the moment, I'll add this to the known bugs list, it will hopefully be fixed in a future release.

The workaround for now is to avoid prodding the beast while a search is running...

If I'm wrong about the cause, and this was caused by a single search click with no more activity, it would help if you could please describe what you were doing.

Cheers,

Jf

Comment 12 Fedora Update System 2013-11-05 22:12:39 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:12 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:13:47 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:38 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 Jean-Francois Dockes 2013-11-06 18:58:44 UTC
Sorry, but NO, the bug was not fixed in 1.19.8, I could not find time to deal with it. See the release notes: http://www.recoll.org/release-1.19.html

Comment 17 Fedora Update System 2013-11-07 03:35:49 UTC
Package recoll-1.19.8-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 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.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20811/recoll-1.19.8-1.fc19
then log in and leave karma (feedback).

Comment 18 Jean-Francois Dockes 2013-11-11 14:36:40 UTC
This is supposedly fixed in recoll 1.19.9, just released.

Comment 19 Fedora Update System 2013-11-23 19:43:25 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 20 Fedora Update System 2013-11-23 19:44:28 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 21 Fedora Update System 2013-11-24 04:04:30 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.