Inline scripts errors does not have any references.

[tkiefer24]

The following error on a page with (Chromium 97, I can see in the logs other browsers also affected):

is tracked as the following payload:

I already tryed the error-stack-parser version 2.x to solve this issue, it does not work!
It would be good to see the filename and lineno property in the logged error message.
I hope someone can fix this.
Thanks,
Timo

[devcorpio]

Hi @tkiefer24,

After investigating I found out that error-stack-parser might have a bug.

        parse: function ErrorStackParser$$parse(error) {
            if (typeof error.stacktrace !== 'undefined' || typeof error['opera#sourceloc'] !== 'undefined') {
                return this.parseOpera(error);
            } else if (error.stack && error.stack.match(CHROME_IE_STACK_REGEXP)) {
                return this.parseV8OrIE(error);
            } else if (error.stack) {
                return this.parseFFOrSafari(error);
            } else {
                throw new Error('Cannot parse given Error object');
            }
        },

For instance:

• if the inline script error happens in Chrome, the logic executed by the library is parseFFOrSafari
• if the inline script error happens in Firefox, the library throws an error and the agent is extracting the stack directly from the value of the ErrorEvent

It is something that we should handle in the agent. An example could be using the lineno,filename and colno as a fallback when creating the stackframe but is something that requires more investigation.

Apart from that, I will open an issue in error-stack-parser repo

Thanks for bringing this to our notice!

[tkiefer24]

@devcorpio mh.. to me it looks more than that the error-stack-parser only got the error property from the ErrorEvent, so it has not enough data that and could not extract filename and lineno information.

[devcorpio]

Hi @tkiefer24,

The release with the fix is now available

Cheers,
Alberto