Bug 724760 – Segfault when try to search by the same term after reloading a document

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 724760 - Segfault when try to search by the same term after reloading a document


Summary:	Segfault when try to search by the same term after reloading a document


Status:	RESOLVED FIXED

Product:	evince
Classification:	Core
Component:	PDF
Version:	git master
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Evince Maintainers
QA Contact:	Evince Maintainers

URL:
Whiteboard:

Depends on:	703595
Blocks:

Reported:	2014-02-20 01:28 UTC by Germán Poo-Caamaño
Modified:	2014-02-25 16:48 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Germán Poo-Caamaño 2014-02-20 01:28:50 UTC

Situation:
- Editing a LaTeX document
- Use Evince to search

1. Search a term (say 'later')
   The sidebar shows a couple of matches
2. Edit the LaTeX document, and add a change that includes
   adding or removing the term searched (in this case, 'later')
3. Compile LaTeX and Evince reloads the document.
4. On the search bar, give the focus to the search entry and press
   <Enter>
5. Segfault

I can reproduce it either adding a term or removing it. Because of
another bug, we know the sidebar is inconsistent.

+ Trace 233195

#0 g_list_length
at glist.c line 918
#1 ev_view_find_get_n_results
at ev-view.c line 7559
#2 ev_view_find_next
at ev-view.c line 7706
#3 ev_window_find_next
at ev-window.c line 4011
#4 g_cclosure_marshal_VOID__VOIDv
at gmarshal.c line 115
#5 _g_closure_invoke_va
at gclosure.c line 840
#6 g_signal_emit_valist
at gsignal.c line 3234
#7 g_signal_emit
at gsignal.c line 3384
#8 egg_find_bar_emit_next
at eggfindbar.c line 214
#9 entry_activate_callback
at eggfindbar.c line 266
#10 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 85
#11 g_closure_invoke
at gclosure.c line 777
#12 signal_emit_unlocked_R
at gsignal.c line 3584
#13 g_signal_emitv
at gsignal.c line 3059
#14 gtk_binding_entry_activate
at gtkbindings.c line 651
#15 binding_activate
at gtkbindings.c line 1523
#16 gtk_bindings_activate_list
at gtkbindings.c line 1584
#17 gtk_bindings_activate_event
at gtkbindings.c line 1669
#18 gtk_widget_real_key_press_event
at gtkwidget.c line 6245
#19 gtk_entry_key_press
at gtkentry.c line 4573
#20 _gtk_marshal_BOOLEAN__BOXEDv
#21 g_type_class_meta_marshalv
#22 _g_closure_invoke_va
#23 g_signal_emit_valist
#24 g_signal_emit
at gsignal.c line 3384
#25 gtk_widget_event_internal
at gtkwidget.c line 6721
#26 gtk_window_propagate_key_event
at gtkwindow.c line 6042
#27 ev_window_key_press_event
at ev-window.c line 6006
#28 _gtk_marshal_BOOLEAN__BOXEDv
#29 g_type_class_meta_marshalv
#30 _g_closure_invoke_va
#31 g_signal_emit_valist
#32 g_signal_emit
at gsignal.c line 3384
#33 gtk_widget_event_internal
at gtkwidget.c line 6721
#34 propagate_event
at gtkmain.c line 2490
#35 gtk_main_do_event
at gtkmain.c line 1716
#36 _gdk_event_emit
at gdkevents.c line 69
#37 gdk_event_source_dispatch
at gdkeventsource.c line 364
#38 g_main_dispatch
at gmain.c line 3054
#39 g_main_context_dispatch
at gmain.c line 3630
#40 g_main_context_iterate
at gmain.c line 3701
#41 g_main_context_iterate
at gmain.c line 3638
#42 g_main_context_iteration
at gmain.c line 3762
#43 g_application_run
at gapplication.c line 1623
#44 main
at main.c line 332

Comment 1 Germán Poo-Caamaño 2014-02-20 01:31:12 UTC

Adding dependency to Bug #703595

Probably fixing that bug, this is going to be fixed as well.

Comment 2 Saurav Agarwalla 2014-02-25 12:39:28 UTC

Hello, there. Bug #703595 is fixed now. So, if that solves this issue too, then maybe we can close this one.

Comment 3 Germán Poo-Caamaño 2014-02-25 16:48:15 UTC

I thought this bug was already closed :-) Thanks for catching this one.