Infinite Calendar Pageload Bug - Only on Month View

I am running NC 24.0.2 on Ubuntu 20.04 server LAMP (php7.4-fpm), Overview has All Checks Passed. I have Calendar calendar: 3.4.0

All apps are functioning correctly except for (my Calendar app).

My custom log – only contains “app” deprecation errors
My NC loggin – only contains “app” deprecation errors
My Apache error log – has no errors besides bots trying to bad things
(i.e. NC records no errors related to this problem in its logs)

If I use browser developer tools, I can clear identify the problematic .js files:

DevTools failed to load source map: Could not load content for Load canceled due to load timeout
DevTools failed to load source map: Could not load content for Load canceled due to load timeout

The specific problem is hat the Calendar page loads infinitely and causes any browser tab to crash (tested in FF and Chromimu on Ubuntu Desktop 20.04)

The bug renders the Calendar Page completely unusable for users.

I have read multiple threads regarding this bug as it appears to be ~2 years old and has persisted across multiple releases of the Calendar App.

However, none of the suggested solutions work and/or are applicable to me.

Things that I have tried:

  1. I disabled Deck and reloaded the Calendar page in browser problem persists
  2. I disabled Circles and reloaded the Calendar page in browser problem persists
  3. I disabled Deck & Circles and reload Calendar page in browser problem persists
  4. I also inspected the oc_properties table via phpmyadmin and did not find applicable entries (errors) that should be delete as to repair this problem according to the above threads.

My oc_properties table contains:

This suggested solution is just not applicable:
select * from oc_properties where propertyname = '{DAV:}resourcetype';

As Calendar is a core app, central to the actual use of Nextcloud as a product, might someone be able to suggest a viable workaround / solution to help me get it running again?


1 Like


I updated the title of the post because this problem only seems to happen when NC Calendar page is loading in Month View in the browser tab regardless of browser

If I switch to List, Week, or Day views, the problem doesn’t exist. If I return to Month view after changing to the different views the problem does not exist.

I normally leave my NC on Calendar view in a chromium tab for easy planning

The specific way to re-create the problem that I have described, is to load the Month View in a new browser tab in any browser.

All other Calendar views opened in new browsers do not cause the infinite pageload bug.

I don’t have this issue… NC 24.0.1 with Calendar AppVersion: 3.3.1… (and I don’t see referenced core-common.js and calendar-main.js in my browser console…)

UPDATE: in my test instance monthly view works with Firefox on NC24.0.2 and Calendar 3.4.0

I did get this issue when upgrading to calendar version 3.4.0 and Nextcloud 24.0.2.

We are having this issue as well, where shared calendars particularly appear to go into a loading loop, in month view.

We have everything in NextCloud on latest stable version (upgraded on Thursday last week).

What I am finding is that my PC (rather than laptop) is running a different version of Chrome (Chrome update icon still visible, where my laptop is on the latest version). My PC does load the calendar month page, but is showing some issues (page crashed when updating a calendar entry, while month view was open).

I look forward to seeing the fix appear ASAP.

Have exactly the same problem after update from 15.0.13 to 24.0.2

Nextcloud: 24.0.2
Calendar: 3.4.0
PHP 7.4.30
Cache: php74-php-pecl-apcu.x86_64 5.1.21-1.el7.remi
OS: CentOS Linux release 7.9.2009 (Core)
OS running as a Proxmox LXC Container, Kernel: 5.4.162-1-pve #1 SMP PVE 5.4.162-2

same here with the monthly calendar view on our self hosted docker instance.
The daily and weekly views are working fine even with several calendars in the view.

for your information, the problem is fixed since version 3.4.1
Do just install the latest version.


Thanks for the follow-up… I keep my app updates on a daily cron job… so fix has definitely been applied. Appreciate the attention to this issue.

Not quite fixed… Perhaps worst? :sob: