While viewing mail from list, delete email, next opens, then closes instantly
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: dmccammishjr, Unassigned)
References
(Blocks 1 open bug)
Details
Comment 1•13 years ago
|
||
Comment 4•13 years ago
|
||
Comment 9•13 years ago
|
||
Reporter | ||
Comment 10•13 years ago
|
||
Reporter | ||
Comment 11•13 years ago
|
||
Reporter | ||
Comment 12•9 years ago
|
||
Reporter | ||
Comment 13•9 years ago
|
||
Updated•8 years ago
|
Reporter | ||
Comment 14•8 years ago
|
||
Reporter | ||
Comment 16•7 years ago
|
||
Reporter | ||
Comment 17•7 years ago
|
||
Comment 18•7 years ago
|
||
Reporter | ||
Comment 19•7 years ago
|
||
Comment 20•7 years ago
|
||
Reporter | ||
Comment 21•7 years ago
|
||
Reporter | ||
Comment 22•7 years ago
|
||
Reporter | ||
Comment 23•7 years ago
|
||
Reporter | ||
Comment 24•7 years ago
|
||
Reporter | ||
Comment 25•7 years ago
|
||
Reporter | ||
Comment 26•7 years ago
|
||
Reporter | ||
Comment 27•7 years ago
|
||
Reporter | ||
Comment 28•7 years ago
|
||
Comment 29•7 years ago
|
||
Reporter | ||
Comment 30•7 years ago
|
||
Reporter | ||
Comment 31•7 years ago
|
||
Reporter | ||
Comment 32•7 years ago
|
||
Comment 33•6 years ago
|
||
Updated•6 years ago
|
Comment 34•6 years ago
|
||
(In reply to Jorg K (GMT+1) from comment #33)
Why is this a dupe of bug 520115 (windows closed after compact). What does this have to do with compacting. New
report just in: Bug 1510783.
But since closed.
So the bottom line of comment 11, in short form, is this bug is NOT compact related?
And is mail.close_message_window.on_delete at the default value of false? Or was it changed to true?
Reporter | ||
Comment 35•6 years ago
|
||
I am seeing this in the current beta 65.0b2 Seemed to have gone away for some time, but reappeared in the last two betas (which came close together). Don't know what other info I can give you.
Interestingly, I have not yet seen the Gloda problem in this beta after a couple of days, but have not pressure-tested it. I'll try to run regression on this build tomorrow for the Gloda problem.
Reporter | ||
Comment 36•6 years ago
|
||
"And is mail.close_message_window.on_delete at the default value of false? Or was it changed to true?" I have not changed any settings and the problem is not consistent so doubt that it is related to some setting. It might happen on the first or second mail read in a series, but then not again in that session. (That is, read, delete, read next, mail window closes, mail item just previously opened is marked read, but not deleted. Open mail, read, delete or move to next for several mail items with no problem.) Since it happens when the system has been "waked up," and thus MIGHT be compacting, then it MIGHT be related.
Reporter | ||
Comment 37•6 years ago
|
||
Using Mozregression gui, I tested 2019-01-10, 2019-01-13 this morning and was not able to make either of them go into the Gloda loop. Both daily builds (66.0a1) DID encounter Gloda errors when compacting, but did not go into an endless loop.
I don't know the build number for 65.0b3, but I have not seen it fail (endless loop of Gloda errors) in normal use.
Comment 38•6 years ago
|
||
(In reply to doug2 from comment #37)
Using Mozregression gui, I tested 2019-01-10, 2019-01-13 this morning and was not able to make either of them go into the Gloda loop. Both daily builds (66.0a1) DID encounter Gloda errors when compacting, but did not go into an endless loop.
I don't know the build number for 65.0b3, but I have not seen it fail (endless loop of Gloda errors) in normal use.
Does it also fail to reproduce when using 67.0b1? (just out)
Reporter | ||
Comment 39•6 years ago
|
||
Don't know build date for 67.0b1, but tested build 2019-03-31 and DID see Gloda infinite loop errors on compact. Have NOT seen Gloda issue in daily use of 67.0b1 (2 days use). Will try to find time later today to run bisection on late March builds.
Reporter | ||
Comment 40•6 years ago
|
||
Gloda running away in 67.0b1 after waking up machine. Appears that "waking up" causes compaction and then Gloda went crazy.
Reporter | ||
Comment 41•6 years ago
|
||
The "wake-up" compaction in 67.0b1 is driving me nuts! It stops use of TBird for at least 30 seconds on my laptop with my settings. If it is "preventive measure" for this bug, it isn't working as such.
Reporter | ||
Comment 42•5 years ago
|
||
This bug is "active" in 69.0b4 on Win10 with mail opened in windows (not tabs). Again, it seemed "dormant" for a while, but now occurs whenever the mail list window has been minimized or quiet for a while. No indication that it is compaction related. Don't see an obvious way to recreate it in mozregression or otherwise capture data. (Not seeing the "wake-up" compaction time noted in comment 41, however.)
Reporter | ||
Comment 43•5 years ago
|
||
Converted to 64 bit 73.0b2 to see if this problem persists - it does. Also, replaced mechanical disk with semiconductor SDD drive. No difference. Symptom continues to be (on this machine!) after any "rest" of TBird (e.g., first use in AM or after any period not using for an hour) the first deleted email triggers closing any open window. I will try tabs (vs. separate windows) to see if any difference.
Updated•5 years ago
|
Comment 44•4 years ago
|
||
from bug 561272 comment 32 ... I believe bug 711204 is also resolved "coincidentally?" in Daily. I have hesitated to close it but have not seen that strange closing window action in a while (which I believe is related to a compaction happening when I first open TBird after a "nap").
Description
•