Some people have reported that this happens every time, almost immediately when Explorer is started. The bug in question though is when Explorer maxes out one CPU core even when you’re not doing anything. I’m thinking about ways to make it more efficient. Some of the operations I’m doing are just CPU-intensive. Note that just using a little more CPU while you’re actually working with Explorer is normal, for now. If you are experiencing this problem, please post the following in the comments: your system specs (OS, CPU, and memory), how frequently you experience the bug, and whether or not you have the “capture new explorer processes” option checked. Unfortunately it’s very difficult for me to fix, as I am unable to reproduce it on any of my test machines. The CPU-leaking bug is currently the most pressing problem with the alpha.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |