Error monitoring tool for recording videos & screenshots of user sessions


Post by pavel »

Hi
RootCause is slowing down my ExtJS 7.0.0 GPL app very much.
It somewhy adds and then removes fieldset-tag after the body-tag dozens of times
Typcical outerHTML of that fieldset tag is as below:

<fieldset><a href="" disabled="disabled"></a><select disabled="disabled"><option></option></select><input type="hidden" name="D"></fieldset>

Sometimes id="sizzleXXXXXXX" atrribute is set up for that fieldset tag
See the screen-video here how it's happening https://www.screencast.com/t/kTh25lQCk6Xr

How this can be fixed?

P.S. seems like feedback section here https://app.therootcause.io/#marc-mittag/translate5/feedback - does not work. I've sent two messages there, but none of them appear in the grid, so i'm even not sure that those messages were successfully sent


Post by pavel »

P.S. XXXXX in "sizzleXXXXXX" - is the timestamp


Post by mats »

Very strange. Can we run this and inspect it ourselves? Can you please post the stacktrace when this fieldset is being added / removed?

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post by marcmittag »

Hi Mats,
I'm leading the development of translate5, where the error occurs, that Pavel, one of our team, did report above.
I would like to give you access to a development instance of translate5, where we can demonstrate you the error.
For what mail address should I create the account?
best
Marc


Post by mats »

You can email it to support at bryntum and we'll have a look - thanks!

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post by marcmittag »

you should have now got an email to set your password and with the URL to the translate5 instance.
Yet please wait to try to reproduce it, we first need to activate theRootCause in the app. Will take perhaps a few hours. Will give you notice then.


Post by mats »

Ok great!

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post by marcmittag »

ok, now theRootCause is active in the app.
As said, you should have received an email to set your password.
Just call this
https://videos.translate5.net/editor/termportal#termportal/search/WyIqIiwiNSIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiIsIiJd/MTY1MjMy
and log in.
Then click the "Process status" combo box in the lower right of the screen. It takes a while, until it opens. The reason is the above described effect, that does only exist, if theRootCause.io is active in the app.

Looking forward to your findings.

Thank you very much

best

Marc


Post by mats »

I observe no such effect. Any more clues on how to repro?

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post by marcmittag »

Hi Mats,
sorry, I had a miss-communication with Pavel.

rootCause.io is slowing down the drop-downs very much everywhere, but the effect he is showing in his video can only be seen in Google Chrome (not in Firefox), when you open the HTML DOM in the debug console and if you call the URL without the search hash, so this URL
https://videos.translate5.net/editor/termportal#termportal

If you watch the opening <html>tag of the page after starting to load it, you will see it blinking.
Also sometimes you can shortly see a fieldset added at the end of the html-dom before the closing </html> tag.

Both only happens, when therootcause.io is active. When we disable therootcause.io, the dropdowns are very fast in opening - like you would expect it.

Since the slowing down of the drop-downs also only happens, when therootcause.io is active, we are pretty sure, that both is connected to therootcause.io and probably to the same cause within it.

The effects of the slowing down you can also observe in Firefox, yet the blinking of the <html>-tag in the dom can not be observed in Firefox console.

I would propose an online session, where we demonstrate it to you. We could use our Zoom account or any tool of your choice.
Afterwards you could use the account I shared with you as long as you need it for debugging.
Makes sense?

best
Marc


Post Reply