Infinate loop while calculating occurance of event, causes browser to freeze #6544

Sergeij2000 · 2024-12-03T11:47:00Z

Steps to reproduce

Set calendar app in month view mode
Subscribe an external (larger) calendar with recurring events

Expected behavior

After a while the events of the new subscription should be shown.

Actual behaviour

New subscription is shown in the calendar list but the busy indicator is frozen and after a while the browser throws an error message. The problem started after upgrading NC from 29.0.6 to 30.0.2

Calendar app version

4.0.7

CalDAV-clients used

NC calendar

Browser

Chrome 131.0.6778.86 and Firefox 133.0-2

Client operating system

Windows 11 and Ubuntu 22.04.1 LTS

Server operating system

Ubuntu 22.04.1 LTS Server

Web server

None

Database engine version

MySQL

PHP engine version

PHP 8.2

Nextcloud version

30.0.2

Updated from an older installed version or fresh install

None

List of activated apps

- activity: 3.0.0
  - app_api: 4.0.0
  - bruteforcesettings: 3.0.0
  - calendar: 5.0.6
  - cloud_federation_api: 1.13.0
  - comments: 1.20.1
  - contacts: 6.1.1
  - contactsinteraction: 1.11.0
  - dav: 1.31.1
  - federatedfilesharing: 1.20.0
  - federation: 1.20.0
  - files: 2.2.0
  - files_external: 1.22.0
  - files_pdfviewer: 3.0.0
  - files_reminders: 1.3.0
  - files_sharing: 1.22.0
  - files_trashbin: 1.20.1
  - files_versions: 1.23.0
  - firstrunwizard: 3.0.0
  - logreader: 3.0.0
  - lookup_server_connector: 1.18.0
  - mail: 4.0.7
  - metadata: 0.21.0
  - music: 2.0.1
  - nextcloud_announcements: 2.0.0
  - notes: 4.11.0
  - notifications: 3.0.0
  - oauth2: 1.18.1
  - password_policy: 2.0.0
  - privacy: 2.0.0
  - provisioning_api: 1.20.0
  - recommendations: 3.0.0
  - related_resources: 1.5.0
  - richdocuments: 8.5.2
  - richdocumentscode: 24.4.902
  - serverinfo: 2.0.0
  - settings: 1.13.0
  - sharebymail: 1.20.0
  - spreed: 20.1.0
  - support: 2.0.0
  - survey_client: 2.0.0
  - systemtags: 1.20.0
  - text: 4.1.0
  - theming: 2.5.0
  - theming_customcss: 1.17.0
  - twofactor_backupcodes: 1.19.0
  - twofactor_totp: 12.0.0-dev
  - unroundedcorners: 1.1.4
  - user_status: 1.10.0
  - viewer: 3.0.0
  - weather_status: 1.10.0
  - webhook_listeners: 1.1.0-dev
  - workflowengine: 2.12.0

Nextcloud configuration

{
    "system": {
        "apps_paths": [
            {
                "path": "\/snap\/nextcloud\/current\/htdocs\/apps",
                "url": "\/apps",
                "writable": false
            },
            {
                "path": "\/var\/snap\/nextcloud\/current\/nextcloud\/extra-apps",
                "url": "\/extra-apps",
                "writable": true
            }
        ],
        "supportedDatabases": [
            "mysql"
        ],
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "memcache.local": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 0
        },
        "log_type": "file",
        "logfile": "\/var\/snap\/nextcloud\/current\/logs\/nextcloud.log",
        "logfilemode": 416,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "***REMOVED SENSITIVE VALUE***",
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "30.0.2.2",
        "overwrite.cli.url": "***REMOVED SENSITIVE VALUE***",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "maintenance": false,
        "mail_smtpmode": "smtp",
        "mail_sendmailmode": "smtp",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpauthtype": "LOGIN",
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "465",
        "app_install_overwrite": [
            "audioplayer_sonos"
        ],
        "loglevel": 3,
        "bulkupload.enabled": false,
        "mail_smtpauth": 1,
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpsecure": "ssl",
        "theme": "",
        "maintenance_window_start": 1,
        "default_phone_region": "DE",
        "defaultapp": "mail,calendar,contacts,files"
    }
}
r

Web server error log

Log file

Browser log

Additional info

The external calendar is imported from your-server.de (Hetzer Horde)
De-installing and re-installing the calendar app (either from UI or occ) doesn't fix the problem, as the faulty calender information seems to be located in the database
I would like to see an occ dav:list-subscription and occ dav:purge-subscription command to be able to clean up the calendar.

The text was updated successfully, but these errors were encountered:

Sergeij2000 · 2024-12-03T11:49:23Z

I forgot to add the screenshot for "actual behaviour":

SebastianKrupinski · 2024-12-03T13:16:25Z

Hi @Sergeij2000

Is there any errors in the nextcloud log?

Sergeij2000 · 2024-12-03T13:34:43Z

No, nothing which could me give a hint what is causing the freeze. I also checked the other logs for php, php-fpm, apache and mysql.

SebastianKrupinski · 2024-12-03T13:36:53Z

Is there anything in the browser console log?

Sergeij2000 · 2024-12-03T13:43:52Z

These are the only entries in the browser console log if i select the files app, clear the console log and then switch over to the calendar app:

session-heartbeat.js:83 session heartbeat polling started
calendars.js:238 calendar home scanned (4) [H, H, H, H] [V] []

SebastianKrupinski · 2024-12-03T14:08:04Z

Okay, I have two more thing for you to try.

Can you clear your browser cache, you can use the disable cache option in the browser tools, then reload the page with the browser tools open.

Do you have any entries in the "properties" table that have a valueType of 3 for this calendar. If so, delete them.

Sergeij2000 · 2024-12-03T14:45:27Z

I disabled the cache and reloaded the page like you told me with the browser tools open, but the properties window stays completely empty.

SebastianKrupinski · 2024-12-03T15:59:14Z

Okay, can you have a look at point # 2?

Sergeij2000 · 2024-12-03T16:19:59Z

I beg your pradon, but which property table do you mean? I thought you mean the properties pane of the browser tools, which is empty...

SebastianKrupinski · 2024-12-03T16:24:12Z

There is a table in the database called "properties" it might be prefixed with "oc_", so it would be something like "oc_properties"

Sergeij2000 · 2024-12-03T16:27:46Z

Thanks for pointing out (i assumed you mean the database after your previous post). As i never accessed the db in nc yet, i need some "finger flexing", which may take some time. I'll report back as soon as i have results...

cu/

Sergeij

Sergeij2000 · 2024-12-03T17:04:40Z

I queried the oc_properties table with SELECT * FROM oc_properies; - and all three subscriptions have valuetype=1

SebastianKrupinski · 2024-12-03T21:22:59Z

Hummm... Not much to go on here to figure out what the issue might be... No PHP errors, no browser errors

I have one more thing to check in the database,
A) can you check if you have any calendar events for that calendar, you will need to match the "id" from the "oc_calendarsubscriptions" table to the "calendarid" in the "oc_calendarobjects" table.
B) can you post a screen capture or output of the "oc_calendars" table and the "oc_calendarsubscriptions" table.

Sergeij2000 · 2024-12-03T21:39:07Z

Oh - thanks for the late answer (der Selbstständige arbeitet selbst und ständig). I will look into the db tomorrow and post results to you. I had another thought: As the difficulties occured after updating NC from 29.0.6 to 30.0.2, the problem might be related to a stale db entry left over from the update. So if you can give me a hint how to purge all old subscriptions, i would like to clean up the db and to start to subscribe to the calendars from scratch. May be this resolves everything.

Nevertheless - thank you for your support!

Sergeij

Sergeij2000 · 2024-12-04T10:21:37Z

Good morning Sebastian,

using your hints regarding the names of the db-tables, i was able to look into oc_calendarobjects with the calendar id of the non working subscription. The calendar contains 3577 events.

I deleted all calendar objects from the db and i was now able to switch to the calendar app, where i deleted the subscription. Then i created a new subscription for that calendar (which is hosted on a Hetzner account). It took some time until the subscription was visible in the calendar list - and then the browser was freezing again.

Next step was, that a changed all recurring events so they have a defined end date in 2050 (i remembered that there was an issue with that), but without success. After deleting and re-subscribing the calendar the browser was freezing again.

Next thing i will try is to reduce the number of events (in the moment the calendar goes back until year 2000) - maybe the problem is the sheer size of the calendar - i'll keep you informed...

Thanks again for your support.

Sergeij

Sergeij2000 · 2024-12-04T12:32:06Z

I think i was able to find something which might cause the problem:

I gradually decreased the size of the calendar by exporting the ics from horde, manually deleting VEVENTs and re-importing the truncated file into horde. But each time i tried to import the calendar into the NC calendar app, the browser was freezing, even if there was only one VEVENT left in the calendar. When i was looking into the ics data delivered from horde, i recognized a strange VTIMEZONE entry, which apparently is created and inserted by horde (because my re-imported ics files didn't contain any VTIMEZONE data). When i looked into my other (working) subscriptions, i couldn't find any TIMEZONE entries - so my educated guess is, that the problem might be caused by these entries.

The VTIMEZONE entry horde is inserting into the ics data looks like:

--------- begin of pasted data -----------------------
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19160501T000000
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19161001T010000
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19170416T030000
RRULE:FREQ=YEARLY;BYMONTH=4;BYMONTHDAY=15,16,17,18,19,20,21;BYDAY=1MO;UNTIL
=19180415T010000Z
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19170917T030000
RRULE:FREQ=YEARLY;BYMONTH=9;BYMONTHDAY=15,16,17,18,19,20,21;BYDAY=1MO;UNTIL
=19180916T010000Z
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19400401T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19421102T030000
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19430329T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19431004T030000
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19440403T030000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1MO;UNTIL=19450402T010000Z
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19441002T030000
TZNAME:CE-T
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19450916T030000
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0300
DTSTART:19450524T030000
TZNAME:CEMT
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19450924T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19451118T030000
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19460414T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19461007T030000
TZNAME:CE-T
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
DTSTART:19471005T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=1SU;UNTIL=19491002T010000Z
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19470406T040000
TZNAME:CEST
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0300
DTSTART:19470511T020000
TZNAME:CEMT
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19470629T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19480418T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19490410T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19800406T030000
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19800928T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19950924T010000Z
TZNAME:CE-T
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19810329T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19961027T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CE-T
END:STANDARD
END:VTIMEZONE
--------- end of pasted data -----------------------

The weird thing is, that this VTIMEZONE thing is not appended to the ics file, but appears somewhere between the VEVENT entries - and there is only one VTIMEZONE entry in the file. Maybe this information helps to locate the problem.

BR

Sergeij

SebastianKrupinski · 2024-12-04T16:38:01Z

Hey,

The timezone entries look fine to me, they are a normal thing in Calendar event, it just describes all the different time transitions from summer to winter time, over the years.

Yes this could be a issue but it probably is not the case.

Is the calendar you are subscribing to sensitive? Would you be willing to share the link, or send it to me privately?

Sergeij2000 · 2024-12-04T16:44:02Z

Do you want a direct link to the calendar or is an ics file dumped from the calendar server sufficient?

Sergeij2000 · 2024-12-04T16:58:44Z

Ok, I've created another account on my server; the calendar contains only one event. (plus the time zone data). If you give me a mail address i pm the link to you. I tried to subscribe to it from NC calendar and the browser was freezing a well. Regarding thr TZ data: I saw several entries with date from 1949 - may this is causing the hickup.

SebastianKrupinski · 2024-12-04T18:40:41Z

Confirmed. The following event causes the UI event phrase to crash.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.6//EN
CALSCALE:GREGORIAN

BEGIN:VTIMEZONE
TZID:Europe/Berlin

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19160501T000000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19170416T030000
RRULE:FREQ=YEARLY;BYMONTH=4;BYMONTHDAY=15,16,17,18,19,20,21;BYDAY=1MO;UNTIL
 =19180415T010000Z
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19400401T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19430329T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19440403T030000
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1MO;UNTIL=19450402T010000Z
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0300
DTSTART:19450524T030000
TZNAME:CEMT
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
DTSTART:19450924T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19460414T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19470406T040000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0300
DTSTART:19470511T020000
TZNAME:CEMT
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19470629T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19480418T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19490410T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19800406T030000
TZNAME:CEST
END:DAYLIGHT

BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19810329T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
END:DAYLIGHT

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19161001T010000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19170917T030000
RRULE:FREQ=YEARLY;BYMONTH=9;BYMONTHDAY=15,16,17,18,19,20,21;BYDAY=1MO;UNTIL
 =19180916T010000Z
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19421102T030000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19431004T030000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19441002T030000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19450916T030000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19451118T030000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19461007T030000
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
DTSTART:19471005T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=1SU;UNTIL=19491002T010000Z
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19800928T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19950924T010000Z
TZNAME:CE-T
END:STANDARD

BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19961027T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CE-T
END:STANDARD

END:VTIMEZONE

BEGIN:VEVENT

DTSTART;TZID=Europe/Berlin:20241216T100000
DTEND;TZID=Europe/Berlin:20241216T110000
DTSTAMP:20241204T180211Z
UID:B969EDE5-83F2-40D0-9614-1EC7624942FC
CREATED:20241204T165208Z
LAST-MODIFIED:20241204T165208Z
SUMMARY:BÃ¼rger Grippeimpfung
CLASS:PUBLIC
STATUS:CONFIRMED
TRANSP:OPAQUE

END:VEVENT

END:VCALENDAR

Not sure why yet.

Sergeij2000 · 2024-12-04T19:38:30Z

Time difference calculations can be pretty nasty: Unix time starts at January 1st, 1970 (ISO: 19700101); the first VMTIMEZONE entry starts at May 5th, 1916 (ISO: 19160501), so the difference gives a negative number!

Just a thought...

Sergeij

SebastianKrupinski · 2024-12-04T19:49:54Z

Diagnosed.

The failure seems to be in a upstream library.

We hand of the iteration calculation to @Nextcloud/Calendar-JS in src/utils/calendarObject.js::getAllObjectsInTimeRange() on line 23.

In @Nextcloud/Calendar-JS/componets/root/eventComponent.js::isInTimeFrame() we hand of the processing to iCal.js which ends up in a infinite loop

Sergeij2000 · 2024-12-04T20:07:34Z

Thanks Sebastian! I've changed the title for the issue as the problem seems to be horde specific...

Sergeij2000 added 0. to triage Pending approval or rejection bug labels Dec 3, 2024

SebastianKrupinski self-assigned this Dec 3, 2024

Sergeij2000 changed the title ~~Subscription of external ics calender link freezes browser~~ Subscription of external ics calender link published by horde freezes browser Dec 4, 2024

SebastianKrupinski added 1. to develop Accepted and waiting to be taken care of and removed 0. to triage Pending approval or rejection labels Dec 4, 2024

SebastianKrupinski removed their assignment Dec 4, 2024

SebastianKrupinski changed the title ~~Subscription of external ics calender link published by horde freezes browser~~ Infinate loop while calculating occurance of event, causes browser to freeze Dec 4, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Infinate loop while calculating occurance of event, causes browser to freeze #6544

Infinate loop while calculating occurance of event, causes browser to freeze #6544

Sergeij2000 commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024 •

edited

Loading

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024 •

edited

Loading

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

Sergeij2000 commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

SebastianKrupinski commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

SebastianKrupinski commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

SebastianKrupinski commented Dec 4, 2024 •

edited

Loading

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

Infinate loop while calculating occurance of event, causes browser to freeze #6544

Infinate loop while calculating occurance of event, causes browser to freeze #6544

Comments

Sergeij2000 commented Dec 3, 2024

Steps to reproduce

Expected behavior

Actual behaviour

Calendar app version

CalDAV-clients used

Browser

Client operating system

Server operating system

Web server

Database engine version

PHP engine version

Nextcloud version

Updated from an older installed version or fresh install

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024 • edited Loading

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024 • edited Loading

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

SebastianKrupinski commented Dec 3, 2024

Sergeij2000 commented Dec 3, 2024

Sergeij2000 commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024 • edited Loading

SebastianKrupinski commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024 • edited Loading

SebastianKrupinski commented Dec 4, 2024

Sergeij2000 commented Dec 4, 2024 • edited Loading

SebastianKrupinski commented Dec 4, 2024 • edited Loading

Sergeij2000 commented Dec 4, 2024 • edited Loading

SebastianKrupinski commented Dec 3, 2024 •

edited

Loading

Sergeij2000 commented Dec 3, 2024 •

edited

Loading

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

Sergeij2000 commented Dec 4, 2024 •

edited

Loading

SebastianKrupinski commented Dec 4, 2024 •

edited

Loading

Sergeij2000 commented Dec 4, 2024 •

edited

Loading