Using UIM with Anki creates defunct processes #102

Open
qsniyg opened this Issue Feb 8, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@qsniyg

qsniyg commented Feb 8, 2017

Using the development version of UIM with Anki creates defunct processes each time I switch to the Anki window (one defunct process when I switch to it, another when I switch away).

If I run anki with QT_IM_MODULE= anki, there are no defunct processes.

@qsniyg

This comment has been minimized.

Show comment
Hide comment
@qsniyg

qsniyg Feb 8, 2017

I should add that I use a text entry function for many of my cards (see https://www.youtube.com/watch?v=5tYObQ3ocrw ).

However, even for a card that has no text entry, simply switching to the next card can lead to 46 extra defunct processes.

qsniyg commented Feb 8, 2017

I should add that I use a text entry function for many of my cards (see https://www.youtube.com/watch?v=5tYObQ3ocrw ).

However, even for a card that has no text entry, simply switching to the next card can lead to 46 extra defunct processes.

@dai-vdr dai-vdr added bug Qt5 labels Feb 8, 2017

@qsniyg

This comment has been minimized.

Show comment
Hide comment
@qsniyg

qsniyg Feb 14, 2017

Anki just got updated under arch linux (which uses PyQt5 instead of, previously, PyQt4), and UIM no longer works, period. I have the latest git version of UIM installed, with Qt5 enabled, and every other Qt5 (and PyQt5) program I have used has worked just fine.

After rolling back to the previous version of Anki (which uses PyQt4 with Python 2), UIM works again, although with the aforementioned defunct process issue.

Interestingly enough, both native and PyQt4 applications (other than Anki) work just fine, without any defunct processes.

I'll file a bug report to Anki as well, because it seems to be something specific about Anki that is causing the problem.

qsniyg commented Feb 14, 2017

Anki just got updated under arch linux (which uses PyQt5 instead of, previously, PyQt4), and UIM no longer works, period. I have the latest git version of UIM installed, with Qt5 enabled, and every other Qt5 (and PyQt5) program I have used has worked just fine.

After rolling back to the previous version of Anki (which uses PyQt4 with Python 2), UIM works again, although with the aforementioned defunct process issue.

Interestingly enough, both native and PyQt4 applications (other than Anki) work just fine, without any defunct processes.

I'll file a bug report to Anki as well, because it seems to be something specific about Anki that is causing the problem.

@dai-vdr dai-vdr added question and removed bug Qt5 labels Feb 15, 2017

@qsniyg

This comment has been minimized.

Show comment
Hide comment
@qsniyg

qsniyg Feb 15, 2017

This is a problem with Qt4/5's Webkit/WebEngine (and is not specific to Anki). While most Qt4/5 applications work fine, those that use QtWebkit/QtWebEngine encounter the issues I described above.

In other words, with a Qt4 Webkit application, defunct subprocesses will appear in the way I described, and with a Qt5 WebEngine application, UIM doesn't work at all.

I will file a bug report to Qt on this issue as well.

qsniyg commented Feb 15, 2017

This is a problem with Qt4/5's Webkit/WebEngine (and is not specific to Anki). While most Qt4/5 applications work fine, those that use QtWebkit/QtWebEngine encounter the issues I described above.

In other words, with a Qt4 Webkit application, defunct subprocesses will appear in the way I described, and with a Qt5 WebEngine application, UIM doesn't work at all.

I will file a bug report to Qt on this issue as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment