5.07 Beta Available (latest version 5.08 RC)

[Craig@Invincea]

Last pass is something see look at as its a very popular addon.

For the most part it's working well for people.
Even the newest 4.0 version

As for those tweaks, that app container flag we cause issues with the chrome sandbox and SBIE.

I know that the Devs (and me) are always testing ahead in browsers and Microsoft Fast Ring builds, but we don't normally test tweaking Chrome settings as part of that. But I will
Mention it. If it was something like v49 of Chrome
Not working after a straight, default install...then that becomes an issue.

[Mr.X]

note: im using some tweaks on Chrome available by : about://flag

i enabled:

- Enable PPAPI Win32k Lockdown.
- Enable AppContainer Lockdown.

note that those tweak were enabled in v48 without issues from Sbie.

As for those tweaks, that app container flag we cause issues with the chrome sandbox and SBIE.

I know that the Devs (and me) are always testing ahead in browsers and Microsoft Fast Ring builds, but we don't normally test tweaking Chrome settings as part of that. But I will
Mention it. If it was something like v49 of Chrome
Not working after a straight, default install...then that becomes an issue.

I still don't understand why to enable those flags. As I mentioned earlier in Wilder's thread under SBIE they seem to have no effect. Am I missing something?
http://www.wilderssecurity.com/threads/ ... st-2558114

[Craig@Invincea]

The Official response from the Dev Team was ".....Don't do that..." in regards to those flags. It can quickly escalate into causing issue with SBIE. Particularly when a setting it affects/may affect Chrome's own sandbox when running within a SBIE sandbox.....

[Mr.X]

The Official response from the Dev Team was ".....Don't do that..." in regards to those flags. It can quickly escalate into causing issue with SBIE. Particularly when a setting it affects/may affect Chrome's own sandbox when running within a SBIE sandbox.....

Thanks for prompt response Craig.

[Craig@Invincea]

The Official response from the Dev Team was ".....Don't do that..." in regards to those flags. It can quickly escalate into causing issue with SBIE. Particularly when a setting it affects/may affect Chrome's own sandbox when running within a SBIE sandbox.....

Thanks for prompt response Craig.

Sure....It should have been more prompt...I saw this thread reply today when it was posted, but I wasn't in the office. I just now remembered the conversation from earlier today I had w/ them..so better late than never.

[Umbra]

The Official response from the Dev Team was ".....Don't do that..." in regards to those flags. It can quickly escalate into causing issue with SBIE. Particularly when a setting it affects/may affect Chrome's own sandbox when running within a SBIE sandbox.....

Thanks for prompt response Craig.

on Chrome v48 it was not a problem, Sbie run fine (i had to downgrade to chrome v48) until a fix ; i think it may be the introduction of new features may create the issue.
i forget to mention that on v49, even by reverting those flags settings to default, the issues remains. i tried many tests before reporting here.

redone the tests:

- Chrome v49 (all settings & flags as default)
- sbie v5.07.5 (with default sandbox)

some extensions crashed and cannot load any pages , get the :

Code: Select all

Fix "Aw, Snap!" page crashes
If you're getting the "Aw, snap" error page, this means that Chrome is having problems loading a webpage you're trying to see. Try the possible fixes below."

i suspect the introduction of the new "Brotli" (page-loading feature) on chrome may be the cause

[Craig@Invincea]

On the "Aw Snap" Page, if you navigate to another page, is everything ok? Or does it force close that page/tab?

[Umbra]

On the "Aw Snap" Page, if you navigate to another page, is everything ok? Or does it force close that page/tab?

all pages are same , at beginning i didn't pay attention, because i thought it was because the extensions crashed but after disabling each of them , every pages get the "aw! snap".

edit:and i cant even acess the extension manager page while sandboxed

[Craig@Invincea]

I think there is something wonky with Chrome 49. I'm getting SBIE 2303 errors IsHungApWindow crash. Same when I attempt to install directly into a SB. v48 and older of Chrome seem to be ok (and I have a lot of extensions in this flavor I'm using...and it's always been ok for me..)

I've let Curt know, but don't count on anything until Monday for them to look @ it.

EDIT: IT appears to be related the the newest FR of Win 10. Seems ok in non-FR version of Win 10. It'll take more testing.

[Umbra]

EDIT: IT appears to be related the the newest FR of Win 10. Seems ok in non-FR version of Win 10. It'll take more testing.

FR meanings?

[Craig@Invincea]

FR meanings?

Fast Ring Dev Build for Win 10. I've fwd my finding to Curt & the Team, if they can recreate what I saw, then it will be looked at more closely.

[Dun]

Did you try to talk to Google or make Chromium patch by yourself to allowing disable Chrome's build-in sandbox as well as yellow bar reminding about it? Disabling Chrome sandbox only if SBIE is detected.
This would make things so much easier and maybe you would have time to fix some non-Chrome issues...

[Craig@Invincea]

Did you try to talk to Google or make Chromium patch by yourself to allowing disable Chrome's build-in sandbox as well as yellow bar reminding about it? Disabling Chrome sandbox only if SBIE is detected.
This would make things so much easier and maybe you would have time to fix some non-Chrome issues...

@Dun. Yep. Good point regarding Chrome / Chromium issue.

As for my issue, The FR Build of Win 10 is causing some headaches. It not only affected Chrome..but everything. My issue is wholly unrelated to this Chrome/flag post.

I just happened to stumble upon it when I was curious about this..which may have uncovered something bigger than turning flags on/off for which....you shouldn't do.

I've sent it to Curt and posted it to the team for further investigation.

[Umbra]

As for my issue, The FR Build of Win 10 is causing some headaches. It not only affected Chrome..but everything. My issue is wholly unrelated to this Chrome/flag post.

I just happened to stumble upon it when I was curious about this..which may have uncovered something bigger than turning flags on/off for which....you shouldn't do.

i didn't say it was related (i did the tests with and without), i mentioned about the chrome//flags only because i enabled them, and for the sake of bugtracking it is more accurate to know the whole picture.

[Peter2150]

I am seeing an error message "Could not hook Ishungappwindow" Hiding it and everything seems normal.

Win 10x64 Fast ring build 14251
Sbie 5.07.5
FF 44