Bug reports connected to the following properties of Home and Small Office products are received in this topic:

— Performance;

— Compatibility with 3rd party soft.

 

Please write in this topic only about the problems that suits the list of components!

General requirements for bug-reports are written in Section 2 of testing guide.

 

All inappropriate messages will be deleted!

 

! | Pay attention:

— Performance should be checked with DISABLED AppVerifier and DrvVerifier tools, and logging noncritical events

— In case of 3rd party soft hang/freezing, manual process' dump is needed or full system dump, else it would be hard to find the roots of the problem

— Sometimes XPerf-logs are needed while checking performance of product.

!!! | Bug reports connected to performance problems on VirtualBox (Oracle®) are not being received[/indent]

!|ALWAYS add traces (product's .log files) to report.

  • Reproduction steps: Open Reports or Manage Applications window, maximize to full screen, scroll or move/hover mouse. This is on Windows 11, but looks similar to my former issue report of KES Beta running on W10.

    Actual result: High CPU load by AVPUI.EXE (one CPU core maxed, another core loaded 50%).

    Expected Result: Low CPU load by AVPUI.EXE.

    Extra note: The initial scan window right after installation also causes AVPUI.EXE to load one CPU core to about 50% (or about half of AVP.EXE, which only seems to use a single-core in this scan). This seems quite high for doing little more than animating a single progress bar.

    Furthermore memory consumption of AVPUI.EXE seems excessively high during a normal "Full Scan". Even worse, when the UI window is closed then memory consumption initially drops, but only after some time and then it builds up again even while the window is still closed.

    (4.16% = 1 CPU core maxed out of 24 logical cores)

    UI load while moving mouse in Manage Applications window: https://imgur.com/xw8STmD

    UI load during initial (post-setup) scan: https://imgur.com/FJ5KCLA

    UI memory during Scan All with window open: https://imgur.com/UArvsgp

    UI memory during Scan all with window closed (keeps going up and down): https://imgur.com/E8nSfov

  • Reproduction steps: Run a selective scan of the C drive. Observe AVP CPU threads.

    Actual result: Only about 4 out of 24 logical CPU threads/cores used. There are more threads created, but these do not process any files for the selective scan (4.16% = 1 core maxed out).

    Expected Result: All 24 logical cores used, or at least the 12 physical cores (depending on SMT/Hyperthreading use).

Looks like your connection to Beta Testing was lost, please wait while we try to reconnect.