I forgot those report, sorry dkellner.Īs I'm currently evaluating which reported UltraEdit issues were fixed in the meantime by IDM, I detected 4 days ago that this bug was fixed with first released version of UE v19.00. This was definitely a bug as the last search string should not be interpreted ever as name of a file to reload. I reported in July 2011 that UltraEdit searches on startup in active working directory several times for a file with name being equal last search string as I could see on a log created with Process Monitor on searching for another issue on startup.
And I knew it was something like seeing a UFO, knowing exactly what everyone will say + think Then I put it back again and the problem appeared again. But there it was, my search string, and I removed it and the problem was gone. It's silly, it sounds like it makes no sense.
Then it also took me a while to figure out (no, randomly pop into) what caused the problem. Of course I know trivial things and I went after this bug quite a bit, including task manager performance monitoring and killing processes one by one - but then it was very clear and very easy to see that the problem was UE itself. That's clear and thank you for the list - but no, what I'm talking about is (was) specific to UE and believe me, I have not the slightest idea of what it could be.
It is nevertheless possible that there is an issue within UltraEdit causing the slower display update and if you find it ever out in a reproducible way, please let IDM know about this issue by email to support. Only 64-bit processes can make use of more RAM at all. Please note that even with 4, 8 or 16 GB RAM on 圆4 machines an out of memory situation can occur easily if all 32-bit processes reach in total its 2 GB limit. Windows is running out of memory and therefore swaps memory to virtual memory on hard disk (pagefile.sys) indicated by a heavy blinking hard disk activity LED.I detected this reason using Sysinternals Process Explorer as this tool displays also the process priority. An application or a driver process is running in a higher task priority than normal and the CPU is a single core CPU for example my company configured McAfee updates being processed with a priority higher than normal which is no problem on a multi-core CPU, but on a CPU with a single core this results in no response of all running applications while the McAfee update in background is in process.My experiences with windows not refreshing quickly or being drawn very slow are caused by: I don't know if the IDM developer has improved something here. I'm not an employee of IDM, I'm just a user like you. Dkellner wrote:This is an ugly, irreproducible bug that you might have fixed already without actually knowing it.