Hi Josiah, Jakub Sitnicki <[email protected]> writes:
> Josiah Schwab <[email protected]> writes: > >> I upgraded to the HEAD of git master, which contains the new thread sort >> code from pull request #455, and immediately began having problems. >> >> Specifically, I receive the following messages (and correspondingly, no >> search results) frequently enough to render mu/mu4e unusable. >> >> ,---- >> | error in process sentinel: mu4e~proc-sentinel: mu server process received >> signal 6 >> | error in process sentinel: mu server process received signal 6 >> `---- >> >> I've boiled the problem down to the following minimal example. >> >> I have a thread with two messages, mailA.eml and mailB.eml, which are >> attached. > > Thanks for making the effort to reproduce the crash. This should make it > easy to add a regression test so that it never happens again. I will > look into it ASAP. Sorry for the delay. Busy week. I was able to reproduce the crash following the instructions you provided. Proposed fix is available in the branch below if you would like to try if it works for you as well: [email protected]:jsitnicki/mu.git thread-sort-fixes Thanks, Jakub >> I'm running these searches at 12:00:00 PDT. One should adjust the date >> range so that only the second message should be included in the results. >> >> If you search for something in the first message, you get the expected >> result (that is, no results): >> >> ,---- >> | monolith: mu$ mu find date:1h..now Apples --skip-dups --threads >> | mu: no matches for search expression (4) >> `---- >> >> If you search for something in the second message, mu throws an error, >> and this appears to be what is eventually reported as "signal 6". >> >> ,---- >> | monolith: mu$ mu find date:1h..now Oranges --skip-dups --threads >> | ** >> | ERROR:mu-container.c:117:mu_container_append_siblings: assertion failed: >> (c) >> | Aborted >> | >> | monolith: mu$ echo $? >> | 134 >> `---- >> >> If I turn on include-related, I get the expected behavior, which is that >> both messages are returned. >> >> ,---- >> | monolith: mu$ mu find date:1h..now Oranges --skip-dups --threads >> --include-related >> | Sat 09 Aug 2014 10:00:00 AM PDT Josiah Schwab <[email protected]> [mu4e] >> Test Message >> | |-> Sat 09 Aug 2014 11:30:00 AM PDT Josiah Schwab <[email protected]> >> Re: [mu4e] Test Message >> `---- >> >> I rolled back to v0.9.9.6 and could not reproduce the problem there. >> >> Best, >> Josiah -- You received this message because you are subscribed to the Google Groups "mu-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
