CPU Problem with /Startup Combined with Spell Check
Posted: Wed Mar 28, 2012 5:37 am
I noticed that sometimes when Notebook loads with the /startup option the notebook.exe process is constantly using 25% CPU (on quad-core system).
After much testing I found it happens when there are at least TWO spelling mistakes on the current sub-section AND the 'Check spelling as you type' is active. One spelling mistake doesn't cause the problem, but 2 or more spelling mistakes causes the CPU problem.
This is how I confirmed the problem :
(1) Have a CPU monitor in the task bar to easily see the constant-CPU problem (I use the graph tray icon from the free 'Process Explorer' program)
(2) Make a shortcut with the /startup option
(3) Create a new blank database. Make sure the 'Check spelling as you type' option is activated.
(4) Test the '/startup' shortcut a few times - CPU usage is normal.
(5) Add some lines of text to the database, it should all be properly spelled - NO spelling mistakes.
(6) Again test the '/startup' shortcut a few times - CPU usage is normal.
(7) Change ONE of the words so there is now ONE spelling mistake.
(8) Again test the '/startup' shortcut a few times - CPU usage is normal.
(9) Change ONE MORE word so there are now TWO spelling mistakes.
(10) Again test the '/startup' shortcut a few times - now CPU is experiencing constant load.
Note that the CPU does automatically return to zero usage when Notebook is Maximized, the CPU is only under load when Notebook is first minimized from the /startup command.
(11) Remove one of the spelling mistakes, so there is again only ONE spelling mistake.
(12) Again test the '/startup' shortcut a few times - CPU usage is back to normal.
(13) Add another spelling mistake so there are again at least 2 mistakes (or more)
(14) Again test the '/startup' shortcut a few times - CPU usage has returned to constant load.
Conclusion : Spelling system causes constant load if 2 or more spelling errors exist in current sub-section AND Notebook is started minimized with /startup command AND 'Check spelling as you type' is active.
After much testing I found it happens when there are at least TWO spelling mistakes on the current sub-section AND the 'Check spelling as you type' is active. One spelling mistake doesn't cause the problem, but 2 or more spelling mistakes causes the CPU problem.
This is how I confirmed the problem :
(1) Have a CPU monitor in the task bar to easily see the constant-CPU problem (I use the graph tray icon from the free 'Process Explorer' program)
(2) Make a shortcut with the /startup option
(3) Create a new blank database. Make sure the 'Check spelling as you type' option is activated.
(4) Test the '/startup' shortcut a few times - CPU usage is normal.
(5) Add some lines of text to the database, it should all be properly spelled - NO spelling mistakes.
(6) Again test the '/startup' shortcut a few times - CPU usage is normal.
(7) Change ONE of the words so there is now ONE spelling mistake.
(8) Again test the '/startup' shortcut a few times - CPU usage is normal.
(9) Change ONE MORE word so there are now TWO spelling mistakes.
(10) Again test the '/startup' shortcut a few times - now CPU is experiencing constant load.
Note that the CPU does automatically return to zero usage when Notebook is Maximized, the CPU is only under load when Notebook is first minimized from the /startup command.
(11) Remove one of the spelling mistakes, so there is again only ONE spelling mistake.
(12) Again test the '/startup' shortcut a few times - CPU usage is back to normal.
(13) Add another spelling mistake so there are again at least 2 mistakes (or more)
(14) Again test the '/startup' shortcut a few times - CPU usage has returned to constant load.
Conclusion : Spelling system causes constant load if 2 or more spelling errors exist in current sub-section AND Notebook is started minimized with /startup command AND 'Check spelling as you type' is active.