I have no problem with a "mu find" that returns 92,000 results using 0.9.9.5.
Empty maildirs may be due to an OS X bug about "related messages". Do you have (setq mu4e-headers-include-related t)? Try nil. -k. On 2014-03-31 at 14:13, Ryan Tate wrote: > On Mar 31, 2014, at 11:05 AM, Ryan Tate <[email protected]> wrote: > >> Hello, I have ~88k messages successfully indexed with mu (successful >> according to `mu index`). However a test search dies after returning >> some very small percentage of what I’d expect the results to be. The >> specific error is “Segmentation fault: 11”. > > FWIW, this segfault seems to be related to very large result sets. If > I search on non-matching terms or terms with only a few dozen matches > (68 in my test case), there is no problem. If I search on very common > terms, e.g. my first name or From, there is a segfault. > > Also, there is no difference in mu output if I run with --debug, > --log-stderr, or both. > > So I have not hit a practical issue with this bug using mu > myself. However I am worried it is impacting mu4e. I am mainly trying > to make sure mu is working right because I am having a separate > problem with mu4e that may (?) be related, where it shows my inbox > (“/new” maildir), but then a few seconds later shows “No matching > messages found.” -- 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.
