256210 - Sunbird no longer starts up,

Status: RESOLVED INVALID

(Calendar :: General, defect)

Description

[Steve Cabito]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Sunbird 0.2

After first install, ran OK 3-4 times, now when starting, grabs 400MB memory and
97% CPU. Too CPU-bound to fully start up. Installed under WinXP SP2.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Marcel Bennett]

Mine never started up at all, but has the same resource hogging issue and left
me with restart as the only option as the process changed every second so I
couldn't kill it within XP's Task Manager before a new version started up. There
was two processes at a time and with a new one created before the first one
finished.

I restarted and still had the same result with no other programs running.

Win XP SP1 w/all updates prior to SP2

Comment 2

[Mostafa Hosseini]

(In reply to comment #1)
> Mine never started up at all, but has the same resource hogging issue and left
> me with restart as the only option as the process changed every second so I
> couldn't kill it within XP's Task Manager before a new version started up. 
This seems more like bug 256206, but Steve's problem seems like an issue with
the cal data.
Steve: Can you attach the ics file which is causing this problem?

Comment 3

[Steve Cabito]

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) 
Gecko/20040803 Firefox/0.9.3
> Build Identifier: Sunbird 0.2
> After first install, ran OK 3-4 times, now when starting, grabs 400MB memory 
and
> 97% CPU. Too CPU-bound to fully start up. Installed under WinXP SP2.
> Reproducible: Always
> Steps to Reproduce:
> 1.
> 2.
> 3.

(In reply to comment #2)
> (In reply to comment #1)
> > Mine never started up at all, but has the same resource hogging issue and 
left
> > me with restart as the only option as the process changed every second so I
> > couldn't kill it within XP's Task Manager before a new version started up. 
> This seems more like bug 256206, but Steve's problem seems like an issue with
> the cal data.
> Steve: Can you attach the ics file which is causing this problem?

After a number of restarts, my problem went away and the app has been behaving 
for a month now.
--

Comment 4

[Matthew (lilmatt) Willis]

No longer can reproduce. 
Marking INVALID. Reopen if new occurences of this bug pop up.

Comment 5

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!