Bug 552445 - pinyin keep crash when CPU load high.
Summary: pinyin keep crash when CPU load high.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peng Huang
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 586292
TreeView+ depends on / blocked
 
Reported: 2010-01-05 04:52 UTC by biAji
Modified: 2010-04-27 08:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 586292 (view as bug list)
Environment:
Last Closed: 2010-04-21 10:26:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description biAji 2010-01-05 04:52:47 UTC
Description of problem:

Can't use pinyin input method when in high cpu load condition. Pinyin keep crashing. You have to restart from applet and after a while , it crashed again.

Version-Release number of selected component (if applicable):

ibus-libs-1.2.0.20091204-2.fc12.i686
ibus-gtk-1.2.0.20091204-2.fc12.i686
ibus-pinyin-1.2.0.20090915-1.fc12.noarch
ibus-1.2.0.20091204-2.fc12.i686

How reproducible:

Do some CPU consuming work, and input characters using ibus-pinyin.


Steps to Reproduce:
1. Do some CPU consuming work
2. input something using ibus-pinyin
3. BOOM!!!
  
Actual results:

it crash again and again. input panel disappear and can't using ctrl-space shortcut to call out pinyin input method again.

Expected results:

nothing special happened

Additional info:

After crash, the daemon complained: 

(ibus-daemon:29976): IBUS-WARNING **: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Comment 1 Peng Huang 2010-01-20 08:45:54 UTC
Please try new ibus.
http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0385

Comment 2 Peng Huang 2010-04-08 02:41:06 UTC
Fixed in ibus-pinyin-1.3.1-1.fc12


Note You need to log in before you can comment on or make changes to this bug.