1129304 - Firefox crashes (segfaults) when I switch to Anthy input method

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[calculuswhiz]

Attachment: Sample zsh terminal run

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150126171358

Steps to reproduce:

When I activate any text-entry box in Firefox, then switch to Anthy (UTF-8), Firefox just crashes. It works fine with my Chinese input method. (This is on Linux). Other GTK applications also run just fine.


Actual results:

Firefox crashes suddenly.


Expected results:

I expect to change input methods and be able to type Japanese. Actually, this has been happening for a while now, but used to work just fine.

Comment 1

[Matthias Versen [:Matti]]

Please provide a crash id from about:crashes (https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report )
note: The Mozilla crash reporter works only with Mozilla.org Firefox builds and probably Ubuntu builds.

Comment 2

[calculuswhiz]

Well, I'm on Arch Linux, so I guess I don't have a crash reporter? But I do have gdb. I attached the process, continued, and got this when I tried to switch:

Program received signal SIGSEGV, Segmentation fault.
0x00007f448423ee49 in ?? () from /usr/lib/libanthydic.so.0
(gdb) bt
#0  0x00007f448423ee49 in ?? () from /usr/lib/libanthydic.so.0
#1  0x00007f448423a4a0 in ?? () from /usr/lib/libanthydic.so.0
#2  0x00007f448423b0c0 in anthy_create_record () from /usr/lib/libanthydic.so.0
#3  0x00007f4484234d59 in anthy_dic_set_personality () from /usr/lib/libanthydic.so.0
#4  0x00007f4484478dab in anthy_do_create_context () from /usr/lib/libanthy.so.0
#5  0x00007f448468599b in ?? () from /usr/lib/uim/plugin/libuim-anthy-utf8.so
#6  0x00007f44c75c7e2f in ?? () from /usr/lib/libuim-scm.so.0
#7  0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#8  0x00007f44c75c85fe in ?? () from /usr/lib/libuim-scm.so.0
#9  0x00007f44c75c8736 in ?? () from /usr/lib/libuim-scm.so.0
#10 0x00007f44c75c7b89 in ?? () from /usr/lib/libuim-scm.so.0
#11 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#12 0x00007f44c75c8298 in ?? () from /usr/lib/libuim-scm.so.0
#13 0x00007f44c75c8506 in ?? () from /usr/lib/libuim-scm.so.0
#14 0x00007f44c75c7e04 in ?? () from /usr/lib/libuim-scm.so.0
#15 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#16 0x00007f44c75d256d in ?? () from /usr/lib/libuim-scm.so.0
#17 0x00007f44c75c7e04 in ?? () from /usr/lib/libuim-scm.so.0
#18 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#19 0x00007f44c75d256d in ?? () from /usr/lib/libuim-scm.so.0
#20 0x00007f44c75c7e04 in ?? () from /usr/lib/libuim-scm.so.0
#21 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#22 0x00007f44c75d4545 in ?? () from /usr/lib/libuim-scm.so.0
#23 0x00007f44c75c7e04 in ?? () from /usr/lib/libuim-scm.so.0
#24 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#25 0x00007f44c75c8298 in ?? () from /usr/lib/libuim-scm.so.0
#26 0x00007f44c75c8506 in ?? () from /usr/lib/libuim-scm.so.0
#27 0x00007f44c75c7e04 in ?? () from /usr/lib/libuim-scm.so.0
#28 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#29 0x00007f44c75c8298 in ?? () from /usr/lib/libuim-scm.so.0
#30 0x00007f44c75c8506 in ?? () from /usr/lib/libuim-scm.so.0
#31 0x00007f44c75c7e04 in ?? () from /usr/lib/libuim-scm.so.0
#32 0x00007f44c75c81a6 in ?? () from /usr/lib/libuim-scm.so.0
#33 0x00007f44c75c892c in ?? () from /usr/lib/libuim-scm.so.0
#34 0x00007f44c73bacfd in GCROOTS_call_with_gc_ready_stack ()
   from /usr/lib/libgcroots.so.0
#35 0x00007f44c75d7583 in uim_scm_callf () from /usr/lib/libuim-scm.so.0
#36 0x00007f44c77f017c in ?? () from /usr/lib/libuim.so.8
#37 0x00007f44c77f0280 in uim_press_key () from /usr/lib/libuim.so.8
#38 0x00007f44c7a086b4 in ?? () from /usr/lib/gtk-2.0/2.10.0/immodules/im-uim.so
#39 0x00007f44db3fd89f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#40 0x00007f44dbc2d255 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#41 0x00007f44dbc3ef4c in ?? () from /usr/lib/libgobject-2.0.so.0
#42 0x00007f44dbc47265 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#43 0x00007f44dbc479bf in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#44 0x00007f44db51499c in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#45 0x00007f44db3fc0bf in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
#46 0x00007f44db3fc47b in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#47 0x00007f44daad4eac in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#48 0x00007f44db958a0d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#49 0x00007f44db958cf8 in ?? () from /usr/lib/libglib-2.0.so.0
#50 0x00007f44db958dac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#51 0x00007f44e2b31d9f in ?? () from /usr/lib/firefox/libxul.so
#52 0x00007f44e2b2ebfb in ?? () from /usr/lib/firefox/libxul.so
#53 0x00007f44e29ac9de in ?? () from /usr/lib/firefox/libxul.so
#54 0x00007f44e29bbbcc in ?? () from /usr/lib/firefox/libxul.so
#55 0x00007f44e29f1dfb in ?? () from /usr/lib/firefox/libxul.so
#56 0x00007f44e30a25f2 in ?? () from /usr/lib/firefox/libxul.so
#57 0x00007f44e31936aa in ?? () from /usr/lib/firefox/libxul.so
#58 0x00007f44e328035e in ?? () from /usr/lib/firefox/libxul.so
#59 0x00007f44e329295c in ?? () from /usr/lib/firefox/libxul.so
#60 0x00007f44e3290dab in ?? () from /usr/lib/firefox/libxul.so
#61 0x00007f44e3290bbf in XRE_main () from /usr/lib/firefox/libxul.so
#62 0x00000000004104b4 in _start ()
(gdb) 

Hm... It says the problem is in `/usr/lib/libanthydic.so.0'. Is this not firefox's issue then? Should I talk to the anthy people?

Comment 3

[calculuswhiz]

(In reply to Matthias Versen [:Matti] from comment #1)
> Please provide a crash id from about:crashes
> (https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report )
> note: The Mozilla crash reporter works only with Mozilla.org Firefox builds
> and probably Ubuntu builds.

Sorry, I accidentally made a new comment instead of replying. See comment 2.

Comment 4

[Matthias Versen [:Matti]]

>Sorry, I accidentally made a new comment instead of replying
just adding a comment is in most cases the better way


As you can see the GDB output for the firefox build is without debug symbols but in this case we do not need debug symbols.

The crash looks really like an issue in Anthy and you should report the issue to them.

Comment 5

[calculuswhiz]

(In reply to Matthias Versen [:Matti] from comment #4)
> >Sorry, I accidentally made a new comment instead of replying
> just adding a comment is in most cases the better way
> 
> 
> As you can see the GDB output for the firefox build is without debug symbols
> but in this case we do not need debug symbols.
> 
> The crash looks really like an issue in Anthy and you should report the
> issue to them.

All right. Thanks for your time.