Desktop application freezes when I use Mozc 1.2.831.102

[GoogleCodeExporter]

What steps will reproduce the problem?

1.Open any desktop application you can input Japanese 
   (eg: gnome-terminal).
2.Type in charactors and terminate the application.

What is the expected output? What do you see instead?

Everything was OK until I was using Mozc 1.1.773.102, but after I 
upgraded to Mozc 1.2.831.102, the application takes a long while to actually 
terminate (almost freezing). After that, I cannot start up any desktop 
application until I terminate Mozc with "killall  mozc_server"
(window manager works OK).

What version of the product are you using? On what operating system?

Mozc 1.2.831.102
Ubuntu 11.04

Please provide any additional information below.

Following is what I got from dmesg output

    [230087.231382] scim-launcher[29364] general protection ip: 334645 sp:bfe9cce0 error:0 in mozc.so[2b8000+e6000]

Actually, I created a new user in my system for test purpose. Mozc 1.2.831.102 
works OK with this new environment.
I am carrying my environment over many years so maybe this is  something to do 
with my setting. However I have no idea about what does this error message mean 
and what should I check with my environment.

Regards

Original issue reported on code.google.com by masayuki...@gmail.com on 9 Sep 2011 at 5:02

[GoogleCodeExporter]

Thank you for the report.

We prepare a patch, but we can't verify it because we can't reproduce the 
problem.
Could you try it and report again?
If the problem is fixed by it, we merge it into a source tree of Mozc.

Temporary, perhaps you can avoid the problem by using iBus instead of SCIM.

Thanks

Original comment by hsum...@google.com on 26 Sep 2011 at 4:30

• Changed state: Started
• Added labels: OpSys-Linux

Attachments:

• mozc_1.2.831.102.patch

[GoogleCodeExporter]

Thank you for the reply.
I tried to apply the patch 

    # mv mozc_1.2.831.102.patch   mozc/src 
    # cd   mozc/src
    # patch   <   mozc_1.2.831.102.patch

and got the following...

    patching file mozc_connection.cc
    Hunk #1 FAILED at 48.
    1 out of 1 hunk FAILED -- saving rejects to file mozc_connection.cc.rej
    patching file mozc_connection.h
    Hunk #1 FAILED at 124.
    1 out of 1 hunk FAILED -- saving rejects to file mozc_connection.h.rej

Am I doing right?

regards

Original comment by masayuki...@gmail.com on 26 Sep 2011 at 5:29

[GoogleCodeExporter]

Thank you for trying patch.

Maybe file paths are wrong.
You can try a patch by following.

# cd mozc/src
# patch -p0 < mozc_1.2.831.102.patch

or

# cd mozc/src/unix/scim
# patch < mozc_1.2.831.102.patch

Thanks

Original comment by hsum...@google.com on 26 Sep 2011 at 5:35

[GoogleCodeExporter]

I applied the patch and mozc is running OK this time.

Thank you very much for your effort.

Original comment by masayuki...@gmail.com on 26 Sep 2011 at 5:48

[GoogleCodeExporter]

Thanks! We have detected the bug correctly by your favor!
This bug is fixed by Mozc-1.2.855.102. (It is released yesterday!)

Unfortunately, the patch contains a little memory leak.
This leak exists on previous version of SCIM Mozc, too.

Now, I make an another patch to correct the crash bug and the memory leak.
Could you try this patch and report again?
I prepare 2 patches. One is for Mozc-1.2.831.102, and another one is for 
Mozc-1.2.955.102.

Original comment by hsum...@google.com on 4 Oct 2011 at 6:48

Attachments:

• mozc_1.2.831.102_2.patch
• mozc_1.2.855.102.patch

[GoogleCodeExporter]

This bug is fixed by r85.

Original comment by hsum...@google.com on 21 Dec 2011 at 8:13

• Changed state: Fixed