Closed Bug 738815 Opened 14 years ago Closed 13 years ago

excessive cpu when attempting to display an inaccessible network calendar

Categories

(Calendar :: Lightning Only, defect)

Product:
Calendar
Component:
Lightning Only
Version:
Lightning 1.3
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 874654

People

(Reporter: hwine, Unassigned)

Details

TB 11 w/ Lightning 1.3 - I added a new network calendar, but with a bad URL. As expected, a "caution" icon is displayed with hover text indicating the calendar is momentarily unavailable. What is not expected is that, as long as the bad URL calender is enabled for display, the CPU usage is excessive, rising to 60-80%. (I spotted this from the thermal alert that caused.)
I can confirm that when an invalid network URL is provided, Lightning will absolutely hammer the server with requests. This has caused problems for us, since we're logging the errors. It quickly fills our logs with GB of data. For example https://calendar.server.com/day/home/calendar@server.com/calendar/ when it should be https://calendar.server.com/dav/home/calendar@server.com/calendar/ (note the "v" instead of "y" in "dav"). This is an innocuous typo that should not result in hundreds of requests per minute.
Shame that this simple but sever bug has been around for more than a year. The related new bug 874654 contains a fix that might solve this problem, too.
Probably just an oversight.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.