Thunderbird 88 on macOS freezes when creating a CalDav calendar
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(thunderbird_esr78 unaffected, thunderbird87 affected, thunderbird88 affected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr78 | --- | unaffected |
| thunderbird87 | --- | affected |
| thunderbird88 | --- | affected |
People
(Reporter: de.berberich, Unassigned)
Details
(Keywords: regression)
Steps to reproduce:
open calendar tab > New Calendar ... > choose "On the network" > fill in username and location (iCloud in my case) > hit "Find Calendars" > fill in password > hit OK
Actual results:
Thunderbird freezes (becomes unresponsive) and no calendar is created.
One must quit Thunderbird via the main menu which is the only menu still working.
Expected results:
Thunderbird should create the CalDav calendar and should not become unresponsive.
The same issue has already been observed when testing TB 87.
|
||
Updated•4 years ago
|
|
|
||
Comment 1•4 years ago
|
||
regression?
|
|
||
Comment 2•4 years ago
|
||
Eckard, can you find the regression range using nightlies?
|
Reporter | |
Comment 3•4 years ago
|
||
I tested a whole lot of Nightlies an d finally found out that the bug appears the first time in Thunderbird 87.0a1 from February 12th, 2021.
( 2021-02-12-10-11-25-comm-central-l10n/ )
|
||
Comment 4•4 years ago
|
||
From 2021-02-11 to 2021-02-12 gives us these regression ranges:
https://hg.mozilla.org/comm-central/pushloghtml?fromchange=02cdb182c49548e5056662d9bebddbbfc553ad6c&tochange=302172a9e62fa393bbe26479749aa3168022ccf3
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=96508d0c910050edc14dd95cd9af86036dac0b90&tochange=67d5bc077f464d338544ad6f27c6ddca858fb286
I'm not seeing anything likely in the comm-central range, and I wouldn't expect anything in mozilla-central to do something like this. Leaving the NI as I need to dig deeper.
|
||
Updated•4 years ago
|
|
|
||
Comment 5•4 years ago
|
||
This should be solved by the patch I've just landed in bug 1713874. I think bug 1685313 is the likely cause. Check it in tonight's nightly build please Eckard.
|
|
Reporter | |
Comment 6•4 years ago
|
||
I tested the tonight's Nightly and could no longer reproduce the issue.
Thank you, Geoff!!
|
|
||
Comment 7•4 years ago
|
||
Thank you, Eckard. I could've found this when you reported it if only I'd not left it sitting in a queue waiting for my attention.
Description
•