Closed Bug 1438452 Opened 6 years ago Closed 6 years ago

Thunderbird hangs after accepting invitation - Daily 60.0a1 (2018-02-13) (64-bit)

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jorgk-bmo, Assigned: Fallen)

References

Details

(Keywords: regression, reproducible)

Attachments

(1 file)

Thunderbird hangs on the "Would you like to send a confirmation e-mail" after accepting invitation regardless of whether you click Yes or No.

I get an "unresponsive script" warning after a while, but cancelling the script doesn't help. CPU is at 25%, looks like one of the four cores runs at 100%, so some endless loop.

Most likely due to recent refactoring in Calendar.
Flags: needinfo?(philipp)
Flags: needinfo?(makemyday)
OK, I tried the build just before the big refactoring in bug 1436557, bug 1436491, bug 1436490, bug 1436488 and bug 1436488 and that already hangs, C-C rev bdfa5f49559e, so the regression is earlier. Alice, can you find it for us, please.
Flags: needinfo?(alice0775)
I tried this in a debug build and I get
JavaScript error: chrome://calendar/content/calendar-unifinder.js, line 449: TypeError: this.tree is null

and later:
JavaScript warning: chrome://lightning/content/imip-bar.js, line 132: Error: Script terminated by timeout at:
getButtons@chrome://lightning/content/imip-bar.js:132:16
resetButtons@chrome://lightning/content/imip-bar.js:121:23
setupOptions@chrome://lightning/content/imip-bar.js:238:9
processFoundItems@resource://calendar/modules/calItipUtils.jsm:1676:9
onModifyItem@resource://calendar/modules/calItipUtils.jsm:1342:13
onAddItem@resource://calendar/modules/calItipUtils.jsm:1348:9
notify@resource://calendar/modules/calDataUtils.jsm:55:32
notify@resource://calendar/modules/calDataUtils.jsm:79:16
adoptItem@file:///C:/mozilla-source/comm-central/obj-i686-pc-mingw32/dist/bin/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calStorageCalendar.js:464:9
addItem@file:///C:/mozilla-source/comm-central/obj-i686-pc-mingw32/dist/bin/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calStorageCalendar.js:412:16
action@resource://calendar/modules/calItipUtils.jsm:1642:36
actionFunc@resource://calendar/modules/calItipUtils.jsm:1667:25
_execAction@chrome://lightning/content/imip-bar.js:350:21
executeAction@chrome://lightning/content/imip-bar.js:463:20
oncommand@chrome://messenger/content/messenger.xul:1:33
(In reply to Jorg K (GMT+1) from comment #1)
> OK, I tried the build just before the big refactoring in bug 1436557, bug
> 1436491, bug 1436490, bug 1436488 and bug 1436488 and that already hangs,
> C-C rev bdfa5f49559e, so the regression is earlier. Alice, can you find it
> for us, please.

please give me STR
Flags: needinfo?(alice0775)
I've sent you and invitation, or you can import this message. Accept the invitation and a panel "Do you want to send a confirmation" comes up. Click Yes or No. Then it hangs.

To repeat, delete the accepted invitation from the calendar, then accept again.
Attachment #8951187 - Attachment mime type: message/rfc822 → text/plain
Blocks: 1434737
Blocks: 1433802
Thanks, Alice!!

I think bug 1434737 was mostly a mechanical exercise, so it's most likely bug 1433802 from the same push. What I don't understand is that there is no test for accepting an event, or if there is, it didn't catch the problem.
Quite likely bug 1433802 as already mentioned. Philipp, if you cannot have a look at it short-termly, we should consider to back out the patch from that bug.
Flags: needinfo?(makemyday)
In that case please prepare a backout patch. Just backing it out gives a warning on calDataUtils.jsm (deleted by other) a few merge conflicts. No surprise given all the refactoring that happened later, see comment #1.
I'm hoping to fix this today, thanks for the investigation.
This might go further back. I can still reproduce this with the treeherder build of bdfa5f49559e which was before the mentioned push. Trying to find out where this starts happening.
Ignore the previous comment, I got the order messed up. Trying to figure out what is going on here.
I'm fixing this in bug 1433802. In hindsight it would have made more sense to use this bug, but I had started with the unit test and a minor fix, and had thought it might be nicer to keep the unit test with the fix.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Flags: needinfo?(philipp)
No worries at all. When the other bug lands, we say "Fixed by bug 1433802" and set the target milestone accordingly :-)
Philipp, can this bug report be marked fixed after the patch in bug 1433802 landed?
Flags: needinfo?(philipp)
Fixed by bug 1433802. Sorry I forgot.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(philipp)
Resolution: --- → FIXED
Target Milestone: --- → 6.2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: