Closed
Bug 114738
Opened 23 years ago
Closed 23 years ago
repeating event causes mozilla to freeze
Categories
(Calendar :: Internal Components, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mikeypotter, Assigned: gray)
Details
Attachments
(1 file, 1 obsolete file)
286 bytes,
text/plain
|
Details |
I will attach teh .oecalendar event file to this bug, but when the file is used,
it hangs Mozilla.
Mostafa: The following was dumped to the terminal:
oeICalImpl::AddObserver()
oeICalImpl::AddObserver()
oeICalImpl::AddObserver()
oeICalImpl::GetEventsForMonth()
(now its frozen (it appears to be in an endless loop)
Reporter | ||
Comment 1•23 years ago
|
||
This is my oecalendar file.
Reporter | ||
Comment 2•23 years ago
|
||
In fact, it appears as though this is just related to the second event from that
file.
I'll add the newer file that obsoletes the other one.
Reporter | ||
Comment 3•23 years ago
|
||
Attachment #61344 -
Attachment is obsolete: true
This is fixed (It was fixed twice actually, Eric and I were both working it,
Eric's stick, mine went to /dev/null).
The code is checked into
cvs.freeassociation.sourceforge.net:/cvsroot/freeassociation.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Opps, that's what I get for marking bugs fixed when tried. I marked the wrong bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Eric fixed this bug. Its checked into the libical CVS store at sourceforge.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Comment 7•22 years ago
|
||
verified
Status: RESOLVED → VERIFIED
Summary: This repeating event causes mozilla to freeze → repeating event causes mozilla to freeze
Updated•19 years ago
|
QA Contact: colint → libical
Updated•19 years ago
|
Component: libical → Internal Components
Comment 8•19 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: libical → base
You need to log in
before you can comment on or make changes to this bug.
Description
•