[Bug]: Logging page freezing/not showing details

[LM-vb]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Nextcloud 29.0.1

After the upgrade from 28.0.5 to 29.0.1 the logging page gets unresponsive/freezes after a certain amount of time (polling?). Additionally, it is no longer possible to show the details (three-dots-menu) of an entry on the logging page. The tab freezes, often crashes. The console gives the following errors (when trying to show details via three-dots-menu):

The bug triggers on different browsers (Chrome, Firefox, Safari).

Steps to reproduce

1. Upgrade to NC 29.0.1
2. Access Administration -> Logging
3. Wait some time resp. try to access the details of an entry in the three-dots-menu

Expected behavior

The page should not freeze/details of an entry should be shown. This worked up until NC 28.0.5.

Installation method

Community Manual installation with Archive

Nextcloud Server version

29

Operating system

Other

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Upgraded to a MAJOR version (ex. 22 to 23)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[Lawkss]

I have same problem mentioned here:

nextcloud/logreader#1262

[Ornanovitch]

Confirmed on my side: same NC version, same console errors

[joshtrichards]

Duplicate of nextcloud/logreader#1262

[Ornanovitch]

Maybe a duplicate, but just notice that there is no firefox crash on our side, just js console errors

[mihailaks]

Confirmed on my side: same NC 29.0.2 version, same console errors