C-C TB crashed when two messages are copied from Inbox folder of one account to another account's Inbox folder. "Do not call the fragment parser (e.g innerHTML()) in chrome code or ..."
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
People
(Reporter: ishikawa, Unassigned)
Details
Attachments
(2 files)
Screen capture from treeherder.
When I try to copy a couple of messages from Input folder of one account to the other's Inbox folder (maildir format),
I get the following crash.
Do not call the fragment parser (e.g innerHTML()) in chrome code or in about: pages, (uri: ), (caller: chrome://messenger/content/multimessageview.js, line: 246, col: 0), (fragment: <div class="star"/><div class="item_summary"><div class="item_header"/><div class="snippet"/></div>)Assertion failure: false, at /NEW-SSD/NREF-COMM-CENTRAL/mozilla/dom/security/DOMSecurityMonitor.cpp:103
#01: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5017e90]
#02: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fd253a]
#03: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fd2db6]
#04: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31eb768]
#05: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31ebd5a]
#06: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4025539]
#07: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4300440]
#08: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7328880]
#09: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734dcb8]
#10: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e7a4]
#11: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e965]
#12: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734f883]
#13: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x777b051]
#14: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x77801c3]
#15: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7318511]
#16: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7345011]
#17: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734d54c]
#18: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e210]
#19: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e7a4]
#20: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e965]
#21: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7485b6c]
#22: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x40b12a7]
#23: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x472b0b3]
#24: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x472fc74]
#25: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4730bd4]
#26: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4730fcb]
#27: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x473376d]
#28: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4733c36]
#29: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x33526cd]
#30: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fc3aa9]
#31: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fc3eb3]
#32: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31e5e57]
#33: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31e6c1a]
#34: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31f10b5]
#35: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x51d76de]
#36: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x51d7aa7]
#37: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x51d9932]
#38: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5bc5868]
#39: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5bcabd7]
#40: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5bcabef]
#41: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x15d35e1]
#42: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x15b7c4c]
#43: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d8b69a]
#44: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d2d91d]
#45: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d2d97b]
#46: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d2dee4]
#47: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x594f391]
#48: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x70a3c49]
#49: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71ee1c1]
#50: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71f014d]
#51: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71f0a65]
#52: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71f2ceb]
#53: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird +0xe50e]
#54: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird +0xe5bc]
#55: __libc_start_main[/lib/x86_64-linux-gnu/libc.so.6 +0x26bbb]
#56: _start[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird +0xda9a]
#57: ??? (???:???)
Program /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird (pid = 308386) received signal 11.
Stack:
#01: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7a5e5c2]
#02: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x849e677]
#03: ???[/lib/x86_64-linux-gnu/libpthread.so.0 +0x13510]
#04: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5017ea1]
#05: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fd253a]
#06: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fd2db6]
#07: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31eb768]
#08: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31ebd5a]
#09: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4025539]
#10: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4300440]
#11: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7328880]
#12: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734dcb8]
#13: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e7a4]
#14: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e965]
#15: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734f883]
#16: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x777b051]
#17: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x77801c3]
#18: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7318511]
#19: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7345011]
#20: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734d54c]
#21: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e210]
#22: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e7a4]
#23: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x734e965]
#24: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x7485b6c]
#25: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x40b12a7]
#26: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x472b0b3]
#27: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x472fc74]
#28: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4730bd4]
#29: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4730fcb]
#30: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x473376d]
#31: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x4733c36]
#32: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x33526cd]
#33: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fc3aa9]
#34: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x2fc3eb3]
#35: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31e5e57]
#36: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31e6c1a]
#37: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x31f10b5]
#38: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x51d76de]
#39: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x51d7aa7]
#40: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x51d9932]
#41: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5bc5868]
#42: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5bcabd7]
#43: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x5bcabef]
#44: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x15d35e1]
#45: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x15b7c4c]
#46: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d8b69a]
#47: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d2d91d]
#48: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d2d97b]
#49: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x1d2dee4]
#50: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x594f391]
#51: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x70a3c49]
#52: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71ee1c1]
#53: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71f014d]
#54: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71f0a65]
#55: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/libxul.so +0x71f2ceb]
#56: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird +0xe50e]
#57: ???[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird +0xe5bc]
#58: __libc_start_main[/lib/x86_64-linux-gnu/libc.so.6 +0x26bbb]
#59: _start[/NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird +0xda9a]
#60: ??? (???:???)
Sleeping for 300 seconds.
Type 'gdb /NEW-SSD/moz-obj-dir/objdir-tb3/dist/bin/thunderbird 308386' to attach your debugger to this thread.
gdb traceback is attached.
|
Reporter | |
Comment 1•5 years ago
|
||
This is with a FULL DEBUG version of C-C TB.
|
|
Reporter | |
Comment 2•5 years ago
|
||
Actually now this crash happens when I simply select TWO messages in the maildir account.
|
||
Comment 3•5 years ago
|
||
Please always check https://treeherder.mozilla.org/#/jobs?repo=comm-central to see if there are current known issues.
|
|
Reporter | |
Comment 4•5 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #3)
Please always check https://treeherder.mozilla.org/#/jobs?repo=comm-central to see if there are current known issues.
*** This bug has been marked as a duplicate of bug 1608872 ***
I see. I didn't realized this breath-taking bug (from the user's point of view) manifested in try server jobs since Jan 13.
It is always time-consuming and rather awkward to co-releate the bug one see on one's PC with a possible bugzialla entry (possibly non-existent because it is noticed for the first time).
Can bugzilla be used in such a way to find the telltale sign of a bug, i.e., the manifestation or symptom explicitly in an easier manner?
In this case, it would be the string.: "Do not call the fragment parser (e.g innerHTML()) ..."
I have myself to blame not including this string in the subject line of the bug, but it would be rather lengthy I though and
omitted it. But may be I should have left it in.
Unfortunately, as far as I can tell both bug 1608872 and the original bug do not mention this string explicitly.
However, bug 1596360 (the original bug) has the attachment and in it,
the string is visible as part of the diff to dom/security/DOMSecurityMonitor.cpp.
https://phabricator.services.mozilla.com/D53163
I have no idea if bugzilla search can look for the string in the attachment for "Do not call the fragment parser" .
If so (and how I wonder), it would make the life of a bug reporter much easier.
I bet there are many duplicates for a newly introduced and already reported bug since a bug reporter facing the bugzilla has tough time
to figure out whether the bug has been reported.
I should have included "Do not call the fragment parser (e.g innerHTML())" probably in the subject/title so that another bug reporter of the same issue would find it immediately.: However, I have noticed that special characters (e.g., ':') and such make the parse string to be invalid and
thus verbatim copy&paste of the error string may not work well. (You can't find it without removing such characters from the search string.)
BTW, I always use the simple bug search field to look for a similar bug, but often there is no indication of a hit (most of the time, actually).
Mozilla may want to spend time to make it easy for bug search (the string search as I mention even including the search in the attachment.: and present it as a simple medium-level search field in the UI if possible.) and reduce the workload of developers and bug triage workers to make it less likely for a bug reporter to reduce the number of simple dupes like this one. (There are legitimate complex cases where duplicated reports may be hard to avoid since a deep cause of a bug many manifest in many variations of symptoms.).
Just a thought. Maybe I should file this comment to request a feature enhancement for bugzilla?
By the way, I don't believe we should ask a bug reporter to look in the try-server jobs.
That will repel the users from TB base.
|
|
Reporter | |
Updated•5 years ago
|
|
|
||
Comment 5•5 years ago
|
||
Sorry, and I agree in general. I was just pointing out to you that since you're filing bugs about new test failures on bleeding edge, then knowing about treeherder is essential as otherwise you will spend a lot of time looking at things that are solved before you figured out what the problem might be. There are often new test failures which will be addressed in following patches (once someone figured them out). If you look at the stars you can see what the bugs associated with the known failures are.
|
|
Reporter | |
Comment 6•5 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #5)
Thank you for your comment.
Sorry, and I agree in general.
I am glad to see someone agree in general.
I was just pointing out to you
Thank you for your tips really.
that since you're filing bugs about new test failures on bleeding edge, then knowing about treeherder is essential as otherwise you will spend a lot of time looking at things that are solved before you figured out what the problem might be.
This is indeed the case. I think I spend about 2/3 of precious time I can spend on TB solving and/or coping with newly introduced issues and some of them are most likely to be solved or noticed by someone already.
BTW, I DID NOT MEAN TO live on the bleeding edge ON MY OWN.
When I noticed some bugs and began trying sending patches several years ago,
I was ADVISED TO USE C-C source tree for creating patches.
I was THANKED for having begun to do so. I was a bit perplexed then.
Now I know why, :-)
There are often new test failures which will be addressed in following patches (once someone figured them out).
If you look at the stars you can see what the bugs associated with the known failures are.
Curious. What "stars" are you referring to?
Is the "star? you mention in the attached screen dump?
I thought it was awkward to figure out if a similar bug was noticed on treeherder if I have to open every
(possibly intermittent) test failures.
One thing I noticed recently.: I may find it easier now to figure out the similar bug with mochitest is that the mochitest of TB run on tree herder seems to print the error line on the error report shown in the lower box when I click on the error(s) shown in the orange color in the list above. This at least makes it easier for me to match the error with the error I see on my local PC after I modify the tree with local patches.
This helps me to confirm if the local problem I see is caused by my local patch or not.
In a sense, if the treeherder simply shows that an error is a known (intermittent) error WITHOUT
showing the original error message itself, it is a way backward in terms of searcheability.
(We have to either click on the bug number OR to open the log to look for the original error message
to ascertain that the bug is really the same bug as one sees locally.)
Thank you again for your attention on this matter.
|
|
||
Comment 7•5 years ago
|
||
(In reply to ISHIKAWA, Chiaki (may be slow to respond until Jan 4.) from comment #6)
I am glad to see someone agree in general.
Heh, yeah I say in general, because treeherder failure status is relevant only for people testing beading. You're one of very few who do that in combination with investigating test failures. Much appreciated that you do!
BTW, I DID NOT MEAN TO live on the bleeding edge ON MY OWN.
When I noticed some bugs and began trying sending patches several years ago,
I was ADVISED TO USE C-C source tree for creating patches.
Absolutely, and many people live on bleading edge. To create patches it's basically a must.
Curious. What "stars" are you referring to?
Is the "star? you mention in the attached screen dump?
No, because that looks to be the try repo which is selected, and there there's no point in starring try runs (and would give wrong stats for failure summaries). Instead look at https://treeherder.mozilla.org/#/jobs?repo=comm-central and you'll notice stars for certain oranges - which mean they have a known cause, or at least tracked in a certain bug which may have more info. Clicking that orange will show will show more data about the failure on the lower left of the screen, like which bug it was associated with.
Let me know if you have more questions about it!
|
|
Reporter | |
Comment 8•5 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #7)
(In reply to ISHIKAWA, Chiaki (may be slow to respond until Jan 4.) from comment #6)
I am glad to see someone agree in general.
Heh, yeah I say in general, because treeherder failure status is relevant only for people testing beading. You're one of very few who do that in combination with investigating test failures. Much appreciated that you do!
BTW, I DID NOT MEAN TO live on the bleeding edge ON MY OWN.
When I noticed some bugs and began trying sending patches several years ago,
I was ADVISED TO USE C-C source tree for creating patches.Absolutely, and many people live on bleading edge. To create patches it's basically a must.
Curious. What "stars" are you referring to?
Is the "star? you mention in the attached screen dump?No, because that looks to be the try repo which is selected, and there there's no point in starring try runs (and would give wrong stats for failure summaries). Instead look at https://treeherder.mozilla.org/#/jobs?repo=comm-central and you'll notice stars for certain oranges - which mean they have a known cause, or at least tracked in a certain bug which may have more info. Clicking that orange will show will show more data about the failure on the lower left of the screen, like which bug it was associated with.
Let me know if you have more questions about it!
Now I know where the star is.
THANK YOU.
These tips ought to be documented somewhere IMHO.
Description
•