Sandboxing of Firefox

Asyn, no problem.
My concern is that if I do not receive help here in avast forum, would I need to post 50+ posts to receive help of avast sandbox BSODing in another forum?

I manage it to work with CIS 5 RC.
Only that is necessary to remove the system virtualization.
I can sandbox Firefox in two levels: partially limited and limited.
Continue to test. Seems I’ll say bye bye to AIS… At least until we can fix it (BSODs and some lack of configurability: exclusion of file types).
I can’t live with BSODs

Tech, why don’t you ask Petr for help ???

I get the impression you only ( try to ) communicate thru the forum, and not directly with the developers :-\ You should try it :wink:

Greetz, Red.

+1. I also had experienced a couple of BSODs recently. I don’t know about you Tech, but I sent my minidump files to pk and he quickly fixed the issue in the internal build. :wink:

Do you think I didn’t?

Red, I’ve done it.
I offered remote connection to my machine.
It could be tested in a virtual environment.
The only handicap is the absence of the dump (due to CTM). I know it’s a huge absence, but they could have tried to simulate this.

No. :frowning: (Am not happy about this lag either…!!)
asyn

okay, I’ve never used CTM, but I’m learning now that it prevents the creation of memory dumps after bsods ??? CMIIW but I suppose this is related to an automatic system restoration by CTM when the system crashes…wow…
back to topic >>> how could Avast devs detect what goes wrong without any dump files, obviously impossible. Okay you know it…
As to simulate it…how? just curious…if they could reproduce on their systems the conditions in which your system failed (while sandboxing), this would mean they already know the cause.

Tech,

If you have those BSOD’s with CTM installed, maybe you should ask the Comodo Devs for help. I have tested CTM from even before the first public BETA ( thnx to one of the Comodo Mods ) but it is a very risky and troublesome technic in my opinion.

Greetz, Red.

yes, not mentioning that indeed CTM could be behind the crashes…

It sure is, heard many complaints, till this day…
asyn

No. When the system crashes, merely nothing is loaded and Windows saves the dump.
But CTM technology needs access to the disk and need to prevent this writing to avoid the snapshots break.
It’s necessary for the technology to work.
I can test CIS and change to AIS in a common boot + 15 seconds. That’s the technology.

Well… I wish they could find a way…

Nor really. The problem is a conflict between the CTM driver and the avast sandbox one. They need to interact for the problem (BSOD) to happen.

I’ve done. No answer also.
https://forums.comodo.com/bug-reports-ctm/ctmfltsys-bsods-0x000000f7-with-175-beta-t58907.0.html

I’m not here to blame nobody. Just to receive some help (I avoid the word, but, maybe, I deserve it… don’t you think?).

okay I had no idea how CTM works, thanks for the heads up.

Nor really. The problem is a conflict between the CTM driver and the avast sandbox one. They need to interact for the problem (BSOD) to happen.

so you’re just confirming what me and Asyn supposed here, that CTM is behind it. What do they say at Comodo? may be they can solve the conflict (although I doubt they would even try ;D )…well my opinion is that Avast shouldn’t take care of that (that’s my opinion ok, no intent to conflict with you here)…why…because Avast is primarily needed on a system, and CTM, for those who want it, comes next…far behind…
And like Asyn said, CTM has such a reputation of breaking systems, I don’t get why you stick to it…

I've done. No answer also

just what I said in my last post :wink: they will never bother trying to resolve a conflict with a competitor. Your issue is between one of their products and one that competes with something they provide too, an IS suite…forget it.

I see no reason for they not do it. It’s difficult for both. In fact, they’ve tried and I’ve in contact with the developers as here with pk.
By “answer” in my post, I meant, solution. Sorry, the post was not fair neither with Comodo nor avast teams.

You really do not trust them. It will be hard for me to convince you.
I believe in freewares. I believe in software development. I try to help when I can.

Seems that you’re wrong…
https://forums.comodo.com/bug-reports-ctm/ctmfltsys-bsods-0x000000f7-with-175-beta-t58907.0.html;msg427131#msg427131

wow, I’m a bit amazed, let’s wait for your feedback when the next release is out then ;D

New Pre-Release Build is now available. I emailed pk and he said he fixed a BSOD issue in this build (if your issue is the same as mine).

They acknowledged it and will fix in next version. Check their forum for details.
It was a problem in the CTM driver and not on the avast sandbox one.

oh I had no doubt that the issue was on Comodo side ;D