Author Topic: History++ UI takes a while to open - possibility for optimization ?  (Read 176 times)

0 Members and 1 Guest are viewing this topic.

Offline VulpixTopic starter

  • Beta Tester
  • *****
  • Posts: 513
  • Country: 00
  • Karma: 13
Hi!

I don't think this is a bug or a regression; rather, I'm curious if there is some room for improvement here.

When I open history++ gui (by clicking on the view history icon), it takes about 2 seconds to pop up. Not too long obviously but when I check it via process monitor, I see that during this time, miranda has made 81 calls to riched20.dll (I assume this is a rich text editor class library).

I saved the "opening of h++ gui" events via process monitor into a text file and checked it for event counts.

Code: [Select]
root@FortressTL-ArcherC7:/home/vulpix/Temp# awk '{print $4}' grepness.txt  | sort -r | uniq -c
   1296 ReadFile
    162 QueryStandardInformationFile
    162 CreateFileMapping
     81 CreateFile
     81 CloseFile
Each call looks like:

Code: [Select]
10:45:57.8212395 Miranda32.exe 2520 CreateFile C:\Windows\SysWOW64\riched20.dll SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
10:45:57.8215056 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 0, Length: 64, Priority: Normal
10:45:57.8215587 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 232, Length: 4
10:45:57.8215903 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 236, Length: 20
10:45:57.8216203 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 480, Length: 40
10:45:57.8216530 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 520, Length: 40
10:45:57.8216817 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 560, Length: 40
10:45:57.8217112 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 600, Length: 40
10:45:57.8217458 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 455 168, Length: 16
10:45:57.8217751 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 455 184, Length: 8
10:45:57.8218051 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 457 560, Length: 2
10:45:57.8218331 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 457 562, Length: 14
10:45:57.8219071 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 455 224, Length: 16
10:45:57.8219413 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 455 240, Length: 8
10:45:57.8219758 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 455 680, Length: 16
10:45:57.8220077 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 455 696, Length: 8
10:45:57.8220407 Miranda32.exe 2520 ReadFile C:\Windows\SysWOW64\riched20.dll SUCCESS Offset: 456 808, Length: 16
10:45:57.8221093 Miranda32.exe 2520 QueryStandardInformationFile C:\Windows\SysWOW64\riched20.dll SUCCESS AllocationSize: 352 256, EndOfFile: 515 072, NumberOfLinks: 2, DeletePending: False, Directory: False
10:45:57.8223305 Miranda32.exe 2520 CreateFileMapping C:\Windows\SysWOW64\riched20.dll FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection: PAGE_EXECUTE|PAGE_NOCACHE
10:45:57.8223776 Miranda32.exe 2520 QueryStandardInformationFile C:\Windows\SysWOW64\riched20.dll SUCCESS AllocationSize: 352 256, EndOfFile: 515 072, NumberOfLinks: 2, DeletePending: False, Directory: False
10:45:57.8224476 Miranda32.exe 2520 CreateFileMapping C:\Windows\SysWOW64\riched20.dll SUCCESS SyncType: SyncTypeOther
10:45:57.8227499 Miranda32.exe 2520 CloseFile C:\Windows\SysWOW64\riched20.dll SUCCESS

I am curious if this couldn't be optimized somehow. It's a super minor thing and maybe not worth investigating, but it just seemed curious that it behaves this way. Might even be a windows "issue". I'm only relaying what I'm seeing, I don't understand it on a level where I could suggest how to improve it or if there is anything to be improved upon.