CPU hogging

[dunkers]

I'm sure someone already mentioned this, but I can't find it in a browse of the forum.

So, here is SEb2 sucking up 12% of a quad core i7 by doing ... nothing. It is sitting there with no editing taking place, and the little thing that tells my what background processes are happening says that nothing is running in background.

Process Monitor shows that it is reading the tag file for the current project. Every second or so it reads another 8192 bytes, and it is currently 74MB into a 76MB file.

The only thing of significance I can think of is that I left my PC for an hour or two with SE open, and the screensave kicked in. On my return I made a change to a file and then noticed the CPU us. I think, but can't be 100% sure, that when I first did something in the SE window (which would be a mouse scroll) it took a few seconds to respond.

[dunkers]

As to the question of what happens when it gets to the end of the file, the answer is this:

Code: [Select]

19:37:48.8205374 vs.exe 40516 ReadFile F:\test\18.0.0\tagfiles\PIC32.vtg SUCCESS Offset: 80,297,984, Length: 8,192
19:37:49.9205824 vs.exe 40516 ReadFile F:\test\18.0.0\tagfiles\PIC32.vtg SUCCESS Offset: 80,306,176, Length: 8,192
19:37:51.0206132 vs.exe 40516 ReadFile F:\test\18.0.0\tagfiles\PIC32.vtg SUCCESS Offset: 80,314,368, Length: 8,192
19:37:52.1206639 vs.exe 40516 ReadFile F:\test\18.0.0\tagfiles\PIC32.vtg SUCCESS Offset: 80,322,560, Length: 8,192
19:37:53.2207648 vs.exe 40516 ReadFile F:\test\18.0.0\tagfiles\PIC32.vtg SUCCESS Offset: 80,330,752, Length: 8,192
19:37:54.3208389 vs.exe 40516 Thread Exit SUCCESS Thread ID: 40248, User Time: 0.0000000, Kernel Time: 0.0000000

I suspect there is another question: did the CPU hogging stop when it got to the end? The answer to that is: no, because it stopped earlier when I had a rootle around my source code.

[Dennis]

When the editor first starts up, we launch a background thread that pre-populates the cache for the database files.  This thread runs at a pretty low priority, but if nothing else is going on, of course, it will get some attention.  Once it has populated the cache, it stops.

[dunkers]

You know your product better than me . SE had been left open for at least a couple of hours when this occured, so I am doubtful that it would be a start-up thing.