HippoEdit is the only application that does not idle

[Arthur]

I started to notice that even if I do not use HE (it is sleeping on the background) the CPU clock never idles. I only have System Idle Process and HippoEdit.exe showing CPU cycles consumed, I am wondering why?

[alex]

take version with PDBs, and check with Process Explorer from Sysinternals call stack and threads of HE at he moment when CPU cycles consumed, but you think should not.
But that can be. HE has some background threads, that works always: for example check for external modified files, saving of the workspace. Also if you have a lot of documents open, background jobs for parsing and stattisctics collection can run rather long time. Even if you already does nothing in HE.

[Arthur]

There is no http://www.hippoedit.com/download/tmp/hippou143_pdb.exe only 1.42
4 docs are open and all saved.

[alex]

Strange, for me this link works http://www.hippoedit.com/download/tmp/hippou143_pdb.exe.
It does not work for you?

[Arthur]

Sorry, got it, but even with the non PDB one I can capture events by Process Monitor: I can see WriteFile events going on crazy for default.hewsp so in my sampling it did 100 writes in less than a hundredth of a second??

[Arthur]

Also messages like NAME NOT FOUND for:
1) HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\Tahoma
2) HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\ListviewScrollOver
3) HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\UseDoubleClickTimer

[alex]

Hm, strange.

What you have in hippoedit.config for WorkspaceAutoSaveDelay:
<WorkspaceAutoSaveDelay>3</WorkspaceAutoSaveDelay>
?

Also messages like NAME NOT FOUND for:
1) HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\Tahoma
2) HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\ListviewScrollOver
3) HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\UseDoubleClickTimer

Ok, I think this is MFC. Hippoedit does not read this directly.

[alex]

In my case everything is fine. The number of file operation is ok.

Sorry, when I tell to use Process Monitor I mean Process Explorer
For it, to see call stack, you need to have pdbs installed.

[Arthur]

Process Monitor is good (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx)

Hm, strange.

What you have in hippoedit.config for WorkspaceAutoSaveDelay:
<WorkspaceAutoSaveDelay>3</WorkspaceAutoSaveDelay>
?
Ok, I think this is MFC. Hippoedit does not read this directly.

<WorkspaceAutoSaveDelay>1</WorkspaceAutoSaveDelay> -- I have 1, I think needs to be higher

[Stefan]

Just to compare
XP SP2 on 1.4 GHz, 2GB RAM
<WorkspaceAutoSaveDelay>3</WorkspaceAutoSaveDelay>

[alex]

to Arthur:

Process Monitor is good (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx)

I know, I have also checked with it.

1 - 3, this is minutes. So even with 1,you should not get 100 saves per second.

[Arthur]

Well, what does it save at all??
My AutoSave is set to "On Application Deactivate", besides the proper English  should be "On application exit".

PS: HE did 17 000 writes in 3 hours, 600 reads, this is too many I think (looked inside Process Explorer).

[Stefan]

PS: HE did 17 000 writes in 3 hours, 600 reads, this is too many I think (looked inside Process Explorer).

All apps do writes and reads all the time. That's common.


> 17 000 writes in 3 hours
6000 per hour
100 per minute
2 every second

Just take a look at ProcMon or FileMon+RegMon, 
it's madness what's going on every second in the back you didn't see 

[alex]

Hi Arthur,

HE access files and uses API functions, which can access registry and all this produce IO.
I am caching what I can, but IO activity any way exist.
And I want to optimize somethin only in case, it creates performance (or nay other) troubles.

So let us leave it like it is untill filnd a really problem.

Also On Application deactivate mean, when application is deactivated (you switch to another application), but not on Application exit

Best regards,
Alex.

[Arthur]

Also On Application deactivate mean, when application is deactivated (you switch to another application), but not on Application exit

Best regards,
Alex.

Still, IMHO the right wording that is more explanatory would be "On Loosing Application Focus" or "On Application Going to Background" then.