Make Importers asynchronous / ICS import causes unresponsive script warning

NEW
Unassigned

Status

Calendar
Import and Export
--
major
5 years ago
4 years ago

People

(Reporter: ziegler, Unassigned)

Tracking

({perf, testcase})

Lightning 1.8
perf, testcase

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 687355 [details]
icalout-new.ics

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121025210744

Steps to reproduce:

I tried to import calendar data stored in an .ics-file, which I had exported before from KOrganizer (KDE calendar program).


Actual results:

I get the following warning 

**********************************************
Unresponsive script

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: file:///usr/lib/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calStorageCalendar.js:2017
***********************************

When I click "Continue" it asks me, which calendar I want to import into, but the dialog is not responsive. Then, after a long time, a new warning pops up:

*********************************
An error occurred when writing to the calendar JoachimsKalender!
Error code: MODIFICATION FAILED
**********************************

and the unresponsive script warning comes back, but can be clicked away.

Updated

5 years ago
Severity: normal → major
Keywords: perf

Updated

5 years ago
Keywords: testcase
I can't reproduce this, but its probably related to cpu vs file size. Confirming because I do see the throbber running. The solution would be to make the importer asynchronous, and possibly bug 302390.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Unresponsive script warning and error when importing an iCalendar (ics) → Make Importers asynchronous / ICS import causes unresponsive script warning
You need to log in before you can comment on or make changes to this bug.