TRIRIGA

Expand all | Collapse all

Chrome and Edge Browser Hanging with Tririga Platform 3.8

  • 1.  Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Wed June 16, 2021 05:23 PM
    Has anyone experienced the chrome Browser hanging on a form that has a collapsed query section? 
    The hang occurs when something is clicked that does a post back to the server

    This appears to have started with Chrome 91.0.4472.101 with platform 3.8

    The steps below will recreate the issue.  This is for the Service Request, but it seems to happen on any form that has a collapsed query section

    To create the issue
    1. Open a Service Request
    2. Collapse The "Assets" or "Other Locations" query section
    3. Close the form
    4. Reopen the form with the collapsed query sections
    5. Click on the "Notifications" tab

    At this point the spinning mouse pointer appears, and the form is hung
    We are seeing exceptions in the Chrome console.  The exception occurs at the time the form is loaded, then again when the action is clicked

    Uncaught DOMException: Blocked a frame with origin "{server url here}" from accessing a cross-origin frame.

    NOTE: If the query sections are expanded, the error does not occur

    ------------------------------
    Robert Nenne
    ------------------------------


  • 2.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Thu June 17, 2021 12:20 PM
    Hi Robert,
    Yes, we are experiencing very similar issues with Chrome (91.0.4472.101 and 91.0.4472.106) and with Edge (91.0.864.48) browsers.  very sporadic with our users (very few are experiencing the problem)...  but the error "Uncaught DOMException: Blocked a frame with origin <our Tririga URL here> from accessing a cross-origin frame." is in the browser's console each time.   We have found a short-term work-around by using Firefox (which, works for our user's experiencing the issue).

    We've also seen (as you have) that if you roll back Chrome to version .77, the error does not occur.  however, as I'm sure you know, as soon as you open chrome, it wants to "update" to the current version again.... (so this is not a workable solution)

    ------------------------------
    Lester Drazin
    ------------------------------



  • 3.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Thu June 17, 2021 12:20 PM
    Robert:

    Yes!
    We have also seen this issue, and it's negatively affecting our user base. 
    Have you submitted a case for this yet? If you have can you either post here, or message me the case number so i can subscribe to the APAR for it?

    Thank you.

    Chris

    ------------------------------
    chris blunk
    ------------------------------



  • 4.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Thu June 17, 2021 12:35 PM
    Edited by Lester Drazin Thu June 17, 2021 12:55 PM
    (edited - adding some additional information/findings)
    Hi Robert,

    Yes, we are seeing the same situation with 3.8.0 and Chrome (91.0.4472.101 and 91.0.4472.106).  We are also seeing the same issue with Edge (91.0.864.48).

    We can also confirm the same DOM error when a form has any section collapsed.  Upon expanding all sections, the issue does not occur.

    Additionally, we have found that Firefox (78.10.1esr) does not exhibit this error (but this could be based on local policy settings).

    We also know that Google just starting pushing out v91.0.4472.101 on 6/9/2021 and v91.0.4472.106 on 6/14/2021.... so others may start to see this as the updates roll out.

    thanks for your post.... we've been trying to correlate this issue for several days.

    This appears to be an issue with platform 3.8.0.

    Regards,

    ------------------------------
    Lester Drazin
    ------------------------------



  • 5.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Mon July 12, 2021 03:41 PM
    Is there a PMR or APAR for this to track ?

    Thanks

    ------------------------------
    Narayanan Ramamurthy
    ------------------------------



  • 6.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted 3 hours ago
    Hi , 

    We are seeing the same exception with platform 3.6.1 now . 

    Uncaught DOMException: Blocked a frame with origin "{server url here}" from accessing a cross-origin frame.

    Chrome94

    Thanks , 

    Parth

    ------------------------------
    Parth Kaushik
    ------------------------------



  • 7.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Thu June 17, 2021 05:09 PM
    Chris,

    I would encourage you to contact IBM as well, as the more people they hear from on this, the more likely this will become a high priority
    I know a ticket has been submitted, but unfortunately, I don't have the number. 
    I'll get in touch with the person who created our ticket and get back to you.

    Bob Nenne

    ------------------------------
    Robert Nenne
    ------------------------------



  • 8.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Fri September 03, 2021 01:45 PM
    Hi Everyone,
    Is anyone still receiving a Lock Icon or Smiley face intermittently after the Chromium Browsers (Edge and Chrome) were updated?

    Thanks 
    John ONeill

    ------------------------------
    John ONeill
    ------------------------------



  • 9.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Thu June 17, 2021 04:09 PM
    Lester,

    Yes we are seeing the same issue in Edge, which make sense since they are both based on the Chromium spec.  Unfortunately using FireFox is not simple as our users would not have the ability to install it and doing a browser rollout would be involved.

    We are hoping that someone, either IBM or Google fixes this quickly. 

    We have thought about changing the setting on the Forms to expanded, but we also believe that the USER_PERSONALIZATION table would have to be updated as if a user changed the setting, it would override whatever is set on the form.  And even then the user could collapse the section again causing the issue to reappear.

    Bob Nenne

    ------------------------------
    Robert Nenne
    ------------------------------



  • 10.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Mon July 12, 2021 03:41 PM
    Hi,

    We just upgraded to 3.8 and are experiencing the same issue. Have you found out anything new since your last update? Did anyone open a PMR?

    Thanks

    ------------------------------
    Gabriel Padilla-Martinez
    ------------------------------



  • 11.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted Wed July 28, 2021 12:10 PM
    FYI, collapsed query section works with the chrome version 92.0.4515.107

    ------------------------------
    Narayanan Ramamurthy
    ------------------------------



  • 12.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted 3 hours ago
    We are no longer experiencing the hanging issue.  We are are on platform 3.8 and Chrome 94.0.4606.81

    ------------------------------
    Robert Nenne
    ------------------------------



  • 13.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted 3 hours ago
    Hi Robert , 

    For us its just not the hanging . We are observing random lock icons/ frowny face in our browser . When we do the inspect element we get the DOM Exception.

    Any insights on this ?

    Uncaught DOMException: Blocked a frame with origin "{server url here}" from accessing a cross-origin frame.

    Thanks , 

    Parth

    ------------------------------
    Parth Kaushik
    ------------------------------



  • 14.  RE: Chrome and Edge Browser Hanging with Tririga Platform 3.8

    Posted 2 hours ago

    Not sure it this is relevant for your case Parth,

     

    But we see (specially with "classic" Tririga modules)... after any chromium update (i.e. Chrome or Edge which both use the same Chromium engine), we have to tell our users to clear their browser's cache.  NOTE – the default "clear cache" is clear the "last hour's" cache.  This does NOT solve the issue.... We have to change the setting to clear cache "ALL TIME" (for both Chrome and Edge) for things to begin working again.  

     

    The issue is that chromium updates come out automatically, and the end-user may not even know that they got an update.   So we use the "Clear Cache – ALL time" as the FIRST error analysis step.   95% of the time, it fixes the issue.

     

    Oh yes, the errors that are seen are "white screen" and nothing happens...  J

     

     

    Long winded answer, but hope this provides some help.

     

    Regards,

    Lester