Closed Bug 1503491 Opened 2 years ago Closed 2 years ago

Remove RemoteSpellcheckEngine.Check sync IPC if possible

Categories

(Core :: Spelling checker, enhancement)

Unspecified
macOS
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- fixed

People

(Reporter: m_kato, Assigned: m_kato)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

When inputting text to <textarea>, it spends a lot of time for sellchecker to wait Chrome process

https://perf-html.io/public/2d42609a638db796e65530e1f3d53bfde8e7c21f/calltree/?globalTrackOrder=0-1-2-3&hiddenGlobalTracks=1-2&localTrackOrderByPid=746-0~&thread=3&v=3

If we can replace RemoteSpellcheckEngine.Check with async IPC, it will improve performance.
dupe of bug 1340573 or bug 1303749 ?

No one uses CheckCurrentWordNoSuggest. So let's remove this IPC!

Assignee: nobody → m_kato

No one uses CheckCurrentWordNoSuggest. So I would like to get a rid of this
method. And this method is only user of mozSpellChecker::CheckWord. So
mozSpellChecker::CheckWord shouldn't allow that aSuggestions is nullptr on
content process since we already have async API as mozSpellChecker::CheckWords.

Let's going away due to unused.

Depends on D19303

Pushed by m_kato@ga2.so-net.ne.jp:
https://hg.mozilla.org/integration/autoland/rev/cd123a9e88f7
Part 1. Remove CheckCurrentWordNoSuggest. r=masayuki
https://hg.mozilla.org/integration/autoland/rev/08b2938c0ea8
Part 2. Remove PRemoteSpellcheckEngine::Check. r=mccr8,masayuki
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.