New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767604 link

Starred by 15 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

New tab Site Can't Be Reached (loadingwithmojo) starts automatically when clicking links to eBay from Outlook

Reported by trikeman...@gmail.com, Sep 21 2017

Issue description

Chrome Version       : 60.0.3112.113
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1.Click on link in email to eBay item from Outlook
2.
3.

What is the expected result?
Item page should come up in new Chrome tab


What happens instead of that?
Item page comes up in new tab, and also, in another new tab, a Site Can't Be Reached Chrome page (for disable-features%3Dloadingwithmojo).


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36



 
Labels: Needs-Triage-M61
Cc: yhirano@chromium.org
Components: Blink>Loader
Labels: Needs-Feedback
Thank you for the report.

Are you disabling "Use Mojo IPC for resource loading" in chrome://flags? Or are you adding the command line flag manually?
Cc: kouhei@chromium.org
Cc: horo@chromium.org
I have seen this issue on varying OS's  win7 through win10.  Another way to replicate the error is create a .url shortcut to a specific website (example facebook.com) with chrome as default browser.  When opening the .url shortcut icon from the desktop it will always produce the 2nd tab with --disable-features%3Dloadingwithmojo 

If you just open google chrome itself, it will not show the error tab - must be done from a .url or link

> #6

I would ask the same question: Are you disabling "Use Mojo IPC for resource loading" in chrome://flags? Or are you adding the command line flag manually?
I have tried using chrome://flags on use mojo and all three settings *default *enabled and *disabled appear to function the same and open the additional tab.

Comment 9 by apwil...@gmail.com, Sep 22 2017

I can confirm the same additional error tab is opened with the address "http://--disable-features%3Dloadingwithmojo/" whenever I launch a web shortcut icon from the desktop. Windows 10 Home 1607 64-bit, Chrome 61.0.3163.100 (Official Build) (64-bit)

Comment 10 by apwil...@gmail.com, Sep 22 2017

Forgot to say, changing the mojo setting in flags to enable/disable/default makes no difference, the error happens regardless of setting.
Thank you.

Could anyone provide a screenshot? Did anyone see the issue before Sep 6? Could anyone test with beta / dev?

Comment 12 by apwil...@gmail.com, Sep 22 2017

Screenshot attached. This only started happening for me in the last few days or so.
Chome Error.PNG
33.2 KB View Download
It sounds like you hadn't heard of the feature before this issue happened, right? Is your browser enrolled in an enterprise policy (i.e., it's office use and managed by IT admins)?
Cc: asvitk...@chromium.org
+asvitkine who reviewed my launch CL (CL 167808446). asvitkine@, have you seen a similar problem?

Comment 15 by apwil...@gmail.com, Sep 22 2017

My PC is personal, home built. No, I'd never heard of this mojo feature before this extra tab started opening recently. It only happens when links are launched externally by the way, such as from an Outlook email or a desktop shortcut, it does not happen when using internal Chrome bookmarks or links with webpages.

Comment 16 by peter@chromium.org, Sep 22 2017

Labels: -Pri-3 Pri-1
People are also reporting this on chromium-dev and in the product forums. Raising to P1.

https://productforums.google.com/forum/#!topic/chrome/-3gLqDEere4;context-place=forum/chrome
My first thought is some third party software is modifying Chrome shortcuts on users' machines and doing it incorrectly causing this effect.

I'm travelling today and OOO next week so can't look at this in more detail right now - but my suggestion is for affected users to inspect their Chrome shortcuts and see if they've been modified this way.
i don't think its the shortcut - i thought the same thing.
Its coming up when users are clicking on links in emails / word etc. so the desktop shortcut is not in use here.
Cc: pbomm...@chromium.org gov...@chromium.org ranjitkan@chromium.org
Cc: jainabhi...@chromium.org
Labels: Hotlist-ConOps
We've also seen 100+ feedback reports since Sept 18, from Chrome versions: 61.0.3163.79 and 61.0.3163.91.


Upon further review, we also found Feedback reports from Chrome version: 60.0.3112.113, and the reporter of this bug is also on 60.113. The very first report we have came in on Sept 18. It looks like this issue is likely not a Chrome regression, but due to an external factor.
Labels: M-60 M-61
Coworker believes it is caused by Trusteer Rapport , anyone with this installed along with the issue that can remove it and see if it was the cause?

Comment 26 by apwil...@gmail.com, Sep 23 2017

I can confirm that Trusteer Rapport does indeed seem to be the culprit.

Rapport's 21 Sept 2017 update (3.5.1804.158) appears to cause the problem. Just Disabling or Deleting their Chrome Extension (release 1.14 / 8 Feb 2016) is not enough to resolve this issue, I had to remove the entire Rapport software completely via Window's Add/Remove Programs, and that has stopped the phantom mojo tabs from being created.

Andre
Opening Trusteer Rapport Console and on the Dashboard

"Rapport is running" (stop)  <-- click on Stop will have same effect as un-installing.

Problem mojo tabs go away, start Rapport again they come back.
Cc: thakis@chromium.org wfh@chromium.org
+  wfh@ (per comment #25, #26 and #27 this is caused by Trusteer Rapport).

Comment 29 by tzik@chromium.org, Sep 25 2017

Found a Trusteer ticket that mentions LoadingWithMojo: https://www.trusteer.com/en/support/google-chrome-mojo-ipc

Comment 30 by rch@chromium.org, Sep 25 2017

Cc: brajkumar@chromium.org
 Issue 767886  has been merged into this issue.
We won't be blocking M61 Stable roll out as this is not M61 regression, caused by Trusteer Rapport and workaround is available at - https://www.trusteer.com/en/support/google-chrome-mojo-ipc.
Cc: abdulsyed@chromium.org

Comment 33 by wfh@chromium.org, Sep 26 2017

That link is likely related to http://shortn/_uSIoTZAvyw (Google access only, sorry) which was fixed a while back, in M55/M56 time period. I suspect this might be a newer issue. I have reached out to Trusteer to see if they have an update on this.

Comment 34 by wfh@chromium.org, Sep 26 2017

Current status:

1. This is a new regression in M61 and appears to be related to trusteer injection into the mojo IPC path and manipulation with messages.

2. Trusteer deployed a workaround fix to disable LoadingWithMojo by appending the commandline "--disable-features=loadingwithmojo".

3. This appears to have caused more/different problems with some users seeing "--disable-features%3Dloadingwithmojo’s server DNS address could not be found." when loading Chrome.

4. We have requested that Trusteer go ahead and disable their mojo injection, as well as the command line injection, until a fix can be found and verified working.
Disabling Trusteer Rapport is not a great idea, since it is a banking security extension that warns of potential security breaches.
Disabling Trusteer Rapport does not fix the problem on its own, because Chrome's flags still have the "--disable-features=loadingwithmojo" flag in the wrong place, as can be seen in chrome://version/
You have to go to chrome://flags/, search for "mojo" and then set "Use Mojo IPC for resource loading" to "Disabled".

Comment 36 by wfh@chromium.org, Sep 27 2017

re: #35 please do not alter Chrome's flags as these changes will last well beyond when Trusteer fix the issue and cause a degradation to your future Chrome experience.

I have heard from Trusteer that a fix for the issue is now rolling out and hopefully should be complete by the end of the week. They have also removed the guidance to change the flag manually from their website, at our request (#c29).

In the meantime, we continue to recommend temporarily disabling Trusteer Endpoint Protection until the issue can be resolved by IBM/Trusteer.
Same issue, even rolled back to v60 from 61, still having the issue and yes we use Trusteer for banking and cannot disable or remove it since we will be unable to access our banking sites.  need a fix here google!

Comment 38 by wfh@chromium.org, Sep 29 2017

Unfortunately there is not much we can do about this since Trusteer runs at a higher privilege level to Google Chrome, so it is not trivial for us to simply prevent them from injecting and manipulating the messages between Chrome processes.

Trusteer have advised us that a fix is in the process of being rolled out and should be completed by Saturday. I advise that you check that you are running the latest version and make sure you have automatic updates enabled.

Comment 39 by wfh@chromium.org, Oct 2 2017

Trusteer have now advised that the version of Endpoint Security that resolves this issue has been rolled out - this is 3.5.1804.161. Please make sure you update your version of Trusteer to this version.

Please also make sure you revert any flags you might have set in chrome://flags - this can be done by clicking the 'reset all to default' button in the top right of the chrome://flags page.
I can confirm the new download of Rapport (Emerald 1804.161) fixes the problem (UK user). Note that you may have to reboot your PC after re-installing it to correctly pick up the new build.

Andre 
I uninstalled Trusteer. I clicked the 'reset all to default' button in the top right of the chrome://flags page, and restarted Chrome.
My Command Line (on chrome://version/) still reads "C:\Users\...\Google\Chrome\Application\chrome.exe" --disable-features=LoadingWithMojo --flag-switches-begin --flag-switches-end

The tab still opens showing:
This site can’t be reached
--disable-features%3Dloadingwithmojo’s server DNS address could not be found.

How does one edit the Command Line directly to remove "--disable-features=LoadingWithMojo", please?
rickraub...@ are you opening Chrome with desktop shortcut? If so, try this:

1. Right click your desktop.
2. Click New > Shortcut.
3. Paste "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" (with double quotes) into the box and click Next.
4. Give the shortcut a name and click Finish.
5. Test the shortcut.
loorong...@gmail.com, I appreciate your helping, but it cannot work. 
In fact, I normally start chrome by clicking a website link in an email; however I also have a shortcut on the taskbar. Its target is C:\Users\Rick\AppData\Local\Google\Chrome\Application\chrome.exe <--please note the lack of any flags here. 
The folder that you suggested I use, "C:\Program Files (x86)\Google\Chrome\Application", does not exist on my laptop: Windows will not let me create that shortcut.

Remarkably, after a reboot, although my Command Line on chrome://version/ still reads
"C:\Users\...\Google\Chrome\Application\chrome.exe" --disable-features=LoadingWithMojo --flag-switches-begin --flag-switches-end
the dreaded --disable-features%3Dloadingwithmojo tab no longer appears when I click a link in an email while Chrome is already open!
I've just received an email stating Trusteer have now advised that the version of Endpoint Security that resolves this issue has been rolled out - this is 3.5.1804.161.

I reinstalled the Trusteer Rapport program but this issue has still not been fixed and whenever I click on a link/URL in email, an additional tab opens on my Chrome browser:  http://--disable-features%3Dloadingwithmojo/

I wish they would get it right!
Try rebooting after installing the latest Rapport software as mine didn't show the new build number (Emerald 1804.161) until after a reboot, even on a full uninstall/reinstall. However once I'd rebooted too it was fine.

Andre
This just in from Trusteer Rapport Technical Support and it worked for me:

Complete the following steps:

1. Please make sure Rapport's Early Browser Protection is enabled.
2. Check for updates.

To Enable Rapport's Early Browser Protection:

a. Open Rapport's Console by choosing - Start Menu > Programs > Trusteer Endpoint Protection > Trusteer Endpoint Protection Console b. Under 'Security Policy' at the bottom right corner, click on 'Edit Policy'. 
c. Enter the letters as they are shown in the image and click OK. 
d. Locate 'Early Browser Protection' and select 'Always' in the drop-down menu. 
e. Click 'Save'.
f. Proceed to the next instructions 

Check for Rapport updates:

a. Open Rapport's Console (Start > Programs > Trusteer Endpoint Protection > Trusteer Endpoint Protection Console) b. Under 'Product Settings', click 'More Settings' 
c. Click 'Check for updates now' 
d. The status of your Rapport updates will appear below in blue letters e. Restart your computer regardless of the status and refrain from using the computer for 15 minutes.
f. Check if the issue is resolved.


Status: WontFix (was: Unconfirmed)
Fixed by Trusteer Rapport.

Sign in to add a comment