A JavaScript error occured in the main process

[dchmelik]

Description

'A JavaScript error occured in the main process' usually pops up over & over.
See also bug 755

2024-4-22 screenshot:

Current behavior

'A JavaScript error occured in the main process' usually pops up over & over.

Expected Behavior

Don't have JavaScript error in main process.

Steps to reproduce

Start jitsi-meet 2022.6.1 (or any for past several months) and leave on such as many hours.

Environment details

Slackware64 15.1-current GNU/Linux, up-to-date

[saghul]

Are you running the app in some kind of special environment?

[dchmelik]

Are you running the app in some kind of special environment?

No.

[saghul]

Then I'm afraid we are in the same situation as #755 , we just don't know what causes that in Slackware. Sorry about that.

[dchmelik]

It's unlikely Slackware-related: I use many electron programs and this is a unique jitsi-meet bug.
        Has it been tested leaving connected to a room 24+hrs including low-bandwidth (such as during large/mass downloads/uploads overnight?)

[saghul]

Not sure what to tell you. We have tested it on many disteis and Slackware is the only one that fails that way AFAIK.

I don't know how leaving a meeting in for 24h has anything to do with this.

When exactly does this happen? Every time? After a while? At a specific time? IIRC the original report didn't have information on that.

[dchmelik]

When exactly does this happen? Every time? After a while? At a specific time? IIRC the original report didn't have information on that.

Always; originally specified 'many hours,' clarified 'overnight'/'24hrs'... don't know anything more exact nor whether low-bandwith is a cause.

[saghul]

Does it happen if the app is open but not doing anything?

[dchmelik]

Does it happen if the app is open but not doing anything?

Usually: usually idle in my room friends are rarely on, and often happens after hours of that or when asleep and find out in morning (can't remember if it happened during discussion in room.)

[dchmelik]

So this happens on Slackware, Kubuntu/Neon (22.04), Mint (21.3, like Ubuntu 22.04 except I use XFCE) and not only overnight, but in more recent weeks/months immediately (before even joining/starting a meeting) and happens on different PCs (different hardware) running these OS and trying jitsi.

[saghul]

Do you have a fresh screenshot?

[dchmelik]

Above is the one I uploaded today.

[saghul]

Oh I missed you updated the original post.

EIO suggests the file descriptor mapped to stdout has gone bad, which doesn't make much sense to me.

I have no idea what's going on :-/

[csett86]

This is really a strange one, I also dug into it and still have no clue how this is happening. But still thank you @dchmelik for continuing to update this ticket that its still occurring...

[dchmelik]

It mainly seems to happen when the PCs (regardless of hardware & OS) have a bit heavier CPU load, though not necessarily even close to 100% (maybe even medium load... I could check later though).