Excessive nonpaged ram usage by "Tag3" for Texstudio when AV enabled [M1016]

A. THE BUG/ISSUE (Varies from issue to issue)
[ol]- Summary - Give a clear summary in the topic subject, NOT here.

  • Can U reproduce the problem & if so how reliably?:
    Almost every time
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened:
    1:Install Texstudio from this link: http://texstudio.sourceforge.net/
    2:Install MiKTex from Portable Edition and install all available packages
    3:If needed set the appropriate paths for the executeables in Texstudio or update the PATH system variable
    4:Open Texstudio and thus the MikTeX package manager
    5:Watch the RAM allocations for Tag3, it will be unusually large.
  • If not obvious, what U expected to happen:
    Not having the nonpaged pool filled for scanning files, which puts the stability of the OS at risk.
  • If a software compatibility problem have U tried the conflict FAQ?:
    Yes, but it did not solve this problem.
  • Any software except CIS/OS involved? If so - name, & exact version:
  • Texstudio (portable, version 2.6.6)
  • MikTeX package manager (portable, version 2.9.4196)
  • Any other information, eg your guess at the cause, how U tried to fix it etc:
    I don’t know whether it’s relevant that all / most latex packages are installed, didn’t try it with a minimal latex installation.
    All intel services are disabled through msconfig.
    mpm.exe and texstudio both hang while quitting until the ram usage is “normal” again.
    It takes about 2 minutes and 30 seconds allocating the ram and about 5 minutes to go down.
    Opening the programms with antivirus disabled does not trigger the excessive ram usage or prolonged time to quit.
    The size of the programm folders total at 3.2GiB.
    [/ol]

B. YOUR SETUP
[ol]- Exact CIS version & configuration:
Version 7.0.317799.4142, standard configuration for the antivirus, also in the attachment

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
    AV - stateful
    Firewall - custom ruleset
    HIPS - Safe mode
    Autosandbox - Fully virtualized; parent folder of the affected programms is in the Bevahior Blocker Exceptions list
  • Have U made any other changes to the default config? (egs here.):
    None which should affect these parts, but the config is attached anyway
  • Have U updated (without uninstall) from CIS 5 or CIS6?:
    No
    [li]if so, have U tried a a clean reinstall - if not please do?:
    NA
    [/li]- Have U imported a config from a previous version of CIS:
    No
    [li]if so, have U tried a standard config - if not please do:
    NA
    [/li]- OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
    Windows 7 Professional, SP 1, 64 bit
    UAC second highest setting
    Account type Administrator
    No virtual machines used during the times.
  • Other security/s’box software a) currently installed b) installed since OS, including initial trial security software included with system:
    a=None b=None
    [/ol]

[attachment deleted by admin]

Thank you for reporting this issue. I have made minor modifications to your first post. Please look it over and let me know if everything looks correct.

Thanks again.

It looks correct, and I added a link and further information about MiKTex.

Roughly how long does it usually take until the excessive RAM usage dies down?

It takes about 2 minutes and 30 seconds allocating the ram and about 5 minutes to go down.

Thank you very much for your report in standard format, with all information supplied. The care you have taken is much appreciated by Comodo, and will increase the likelihood that this bug can be fixed.

Developers may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.

Many thanks again.

The devs have not marked this as Fixed in the tracker. However, sometimes bugs are fixed by the release of new versions, but not marked as Fixed in the tracker.

If you are able please check with the newest version (CIS version 8.0.0.4337) and let me know if this is fixed on your computer with that version.

Thank you.

Hello,

The devs have not marked this as Fixed in the tracker. However, sometimes bugs are fixed by the release of new versions, but not marked as Fixed in the tracker.

If you are able please check with the newest version (CIS version 8.1.0.4426) and let me know if this is fixed on your computer with that version.

Thank you.

Please check to see if you still have this issue with CIS 10.0.0.5144 Thanks.

This should be fixed with Comodo Internet Security V10.0.0.6071 Beta if you are still experiencing this issue please make a reply thanks.