418100 - Lightning fails to parse its own ICS file

Status: RESOLVED INCOMPLETE

(Calendar :: Provider: ICS/WebDAV, defect)

Description

[dekkerdreyer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Thunderbird version 2.0.0.9 (20071031) Lightning 0.7

Attempting to open thunderbird causes this error:

[Exception... "Component returned failure code: 0x804a0107 [calIICSService.parseICS]"  nsresult: "0x804a0107 (<unknown>)"  location: "JS frame :: file:///C:/Documents%20and%20Settings/me/Application%20Data/Thunderbird/Profiles/9066d8ci.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/js/calIcsParser.js :: ip_parseString :: line 60"  data: no]

Reproducible: Always

Steps to Reproduce:
1. Start Thunderbird
2.
3.

Comment 1

[Stefan Sitter [:ssitter]]

Please provide detailed steps to reproduce the issue starting with a clean profile or attach an .ics testcase if possible.

Comment 2

[dekkerdreyer]

I believe this is an incomplete ICS writing issue.  Unfortunately I do not have the ICS anymore.  Thunderbird went to 100% cpu while trying to update the calendar after I added an event.  I didn't notice until I was writing an email a few minutes later.  I had to terminate Thunderbird, and this probably caused the botched ICS write.  Implementing safe writes (writing to a temp file and then renaming) would really help here.

I don't really have any more information, so this is probably a dud bug report.

Comment 3

[Omar Bajraszewski]

(In reply to comment #0)
 
> [Exception... "Component returned failure code: 0x804a0107
> [calIICSService.parseICS]"  nsresult: "0x804a0107 (<unknown>)"  location: "JS
> frame ::
> file:///C:/Documents%20and%20Settings/me/Application%20Data/Thunderbird/Profiles/9066d8ci.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/js/calIcsParser.js
> :: ip_parseString :: line 60"  data: no]
> 
I can see similar error in bug 387238, bug 387890. 

Comment 5

[Bas van den Bosch]

(In reply to comment #2)
> Implementing safe writes (writing to a temp file and
> then renaming) would really help here.

I think the caching-mechanism will provide this. 

Comment 6

[Daniel Boelzle [:dbo]]

Makes hardly any sense if we are lacking more information; please reopen if you have more.