Virtual_mode_helper does not close when I close Dragon [M382] [v6]

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
#1

After closing down Virtual Dragon Browser, Virtual_mode_helper.exe does not shut down. If I start another Browsing session with Virtual Dragon, another instance of virtual_mode_helper.exe is created. It will keep doing this unless I forcibly kill the process through task manager. This appears to be a bug.

Windows 7 SP1 64bit

#2

Thank you very much for your issue report.

We would very much appreciate it if you would be kind enough to edit your report to put it in the standard format and add any additional information requested, as this will make it much easier for the developers to diagnose and fix the problem.

The reasons we need all the information in the format, though they may not seem directly relevant to the issue are explained here.

If you are able to do this we will forward this post to the format verified board, where it is more likely to get looked at by developers. You can find assistance using red links in the format and here. If you need further help please ask a mod. If you do not add the information after a day or two we will forward this post to the non-format board. If this happens we will tell you how to rectify this if you wish to.

In the current process we will normally leave it up to you whether you want to make a report in standard format or not. However we may remind you if we think a bug of particular importance.

Many thanks again

Mouse

#3

PM sent

#4

Thanks very much for your issue report, which is much appreciated.

We have moved it to the non-format bugs board for the moment, because it is not in the standard format or too much of the information we normally need to replicate a problem and fix it is still missing.

We realize some people may not have the time to do an issue report in standard format, and therefore offer the option of a non-format report instead. But the problem is much more likely to be fixed promptly if you edit your first post to create an issue report which reflects the guidance in the Standard Format topic. (You can copy and paste the format from this topic). The reasons we ask for the information we do are given in this post.

You can get your report moved to the format verified issues board simply by ensuring that it reflects the guidance in the standard format topic, and PM’ing a mod who is active on the bug board.

Best wishes

Mouse

#5

Can you please check and see if this is fixed with the newest version (version 6.2.282872.2847)? Please let us know whether it is fixed or you are still experiencing the problem.

Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments, so I can forward this to the devs and get this problem fixed.

Thank you. PM sent.

#6

I will move this to the main bug reporting section and re-evaluate this bug report as I can confirm this behavior.

#7

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?:
    Yes, every time.
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened:
    Open Windows task manager. Then open Comodo Dragon through the widget. Note that in the task manager a process labeled “virtual_mode_helper.exe32" is created. Close the virtualized instance of Comodo dragon and the process stays. Then, open Comodo Dragon once again through the widget. A second instance of "virtual_mode_helper.exe32” is created, but the original is not closed. This also stays if you close the virtualized instance of Comodo Dragon. These do not go away, even if the FV sandbox is reset. Only a system restart gets rid of them.
  • If not obvious, what U expected to happen:
    After CD is closed the process should be closed as well. Duplicates should not be created, and even if they are they should definitely be killed when the sandbox is reset.
  • If a software compatibility problem have U tried the conflict FAQ?:
    NA
  • Any software except CIS/OS involved? If so - name, & exact version:
    NA
  • Any other information, eg your guess at the cause, how U tried to fix it etc:
    I do not have an idea of what causes this vulnerability.
  • Always attach - Diagnostics file, Watch Activity process list, dump if freeze/crash. (If complex - CIS logs & config, screenshots, video, zipped program - not m’ware)
    I have attached a diagnostics report and a KillSwitch process dump (both of which were done when CD had been closed the second time and both processes still existed). A screenshot of the two processes is also attached.
    [/ol]

B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- Exact CIS version & configuration:
CIS version 6.2.282872.2847
Default Configuration

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
    Default Configuration
  • Have U made any other changes to the default config? (egs here.):
    Default Configuration
  • Have U updated (without uninstall) from a CIS 5?:
    No, this was a clean install.
    [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 x64 (fully updated), UAC disabled, Real System, run as administrator.
  • Other security/s’box software a) currently installed b) installed since OS: a)
    None b) none
    [/ol]

[attachment deleted by admin]

#8

Can you please check and see if this is fixed with the newest version (6.3.294583.2937)? Please let us know whether it is fixed or you are still experiencing the problem.

Thank you.

PM sent.

#9

Actually, I was able to test this, and it appears that this is fixed for CIS version 6.3.294583.2937.

Thus, I will move this to Resolved.