MyInfo Community Forums

I just upgraded from 4.0.1 to 4.0.2 and now MyInfo uses 100% CPU even when idle. I rebooted and problem persists. This is the only change I've made to my system today.

Can I go back to 4.0.1? Is that just a matter of re-running the 4.0.1 installer (which I still have) on top of existing 4.0.2 or does that not work?

Thanks,
Jay

Yes, you can downgrade to 4.01 by installing the old version over the new one.

However I would like to learn more about the problem. How many topics do you have open in MyInfo? Is there anything other that is specific and could lead to this problem (like editing very large text file)?

We need this information in order to investigate that problem.

I can't think of anything unusual. I have eight topics. The largest one is 200k. The entire My Topics folder is 2meg. Even after closing all topics, the problem persists. Then if I close MyInfo (via Exit) and wait for it to disappear in Task Manager, and restart MyInfo (with no topics), it goes back to top of the list at >95% CPU and stays that way for hours until I shut it down. I've got plenty of free memory and I'm not running any other applications. This problem started after upgrading to 4.0.2.

I downgraded to 4.0.1 and problem goes away.

Could the usage percentage be coming from keeping track of the Date/Time in the Due Date Column of the Tree. I noticed that the items changes color right on time so you must be checking the variable quite often.

Just throwing out a thought.

<Ralph>

It turns out that the problem is in the live spelling. We are working to fix this ASAP.

Meanwhile, you can use 4.02 without the CPU problem, if you disable Check Spelling As You Type option.

Interesting.
I reinstalled 4.02 and noted the high CPU usage, then I removed the option for live spelling like you said and the usage returned to normal.
For the heck of it I turn the live spelling back on and the usgae remained normal. Thought I'd share that.

<Ralph>

Ralph, we have just sent out the update, which fixes the problem. But you are right - this was a possible workaround.

Thanks for the quick response! I downloaded the latest 4.0.2, installed over existing version, and problem goes away.