-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
betterbird-128.5.0esr-bb18 Segmentation fault (core dumped) #380
Comments
What a nasty report 😢 That's going to be difficult, since BB does't have crash reporting and the problem doesn't happen in TB which does have crash reporting. We're not aware of any changes wrt. to IMAP messages downloading. And since this needs access to your IMAP folder, we won't be able to reproduce the issue. Can you operate the Linux debugger? In that case we can compile a debug version and you can provide a stack-dump when the crash happens. |
You haven't stated your desktop environment. If it's Gnome, you're likely suffering from Issue #266. Follow the suggestions from #275 (comment)? |
Thank you. Yes my desktop Environment is Gnome. I had only mail.minimizeToTray on true. Now changed to false. Will test and come back. (I would also be able for basic Linux debugger handling if that helps ) |
If it's the Gnome crash, there is no point debugging it, since it crashes in Gnome. I valuely remember that we have a pref to prevent the crash from happening. It contains the incompatible DEs, from memory "gnome,ubuntu:gnome". When you run BB from the command line, which DE does it report? That should be added to the pref. |
It happened once again but it took maybe longer. All settings with tray:
that are all messages I get at the commandline:
|
I started it with gdb this results in the following output:
|
Without a debug build with symbols using gdb won't get us anywhere. So it crashed before it even reports the DE? You said that it only crashes online, so start it offline. This is what it reports at startup for me, see the last line:
BTW, while looking for ADDITION: I'm pretty sure we can't action this, it's some issue somewhere in some graphic library in the plethora of variations that make up the Linux zoo. As I've written elsewhere, Linux provides the project with 2% of its income and 98% of its problems 🤣 - Don't take it too seriously, lots of nice and competent users on Linux, that compensates a bit. |
It does not report any desktop environment. The complete output is :
btw my desktop environment is now kde but same error ... |
Right, looking at the code again, when pref mail.biff.show_tray_icon isn't set, then the code that reports the DE isn't run at all, since then we don't touch the system tray. KDE actually works well with the BB system tray implementation. We'll build you a debug build, then you can get a crash stack. |
Thank you ! It took some time till the crash occurs. I got the following output:
Stack info :
|
I'm not a gdb expert, what's the command gdb backtrace, bt or where? That stack shows nothing. It should show symbol information to see where it crashed. Where you doing anything in particular at the time of the crash? And if the crash "took some time", how do you know that TB wouldn't also crash? There are plenty of crashes in TB. I suggest you try creating an new profile, I can't tell what's happening. |
Update and answering your questions:
backtrace/bt is identical to info stack
no it does not matter what I do ... the only coincidence for the error is that it happens if there is a bunch of imap Mails that are synchronized ... I assume more than 10 in one account are needed for the crash
Currently Iam forced to use Thunderbird 128.5.1 instead of BB as my daily driver. Till now there was no crash happening in TB (only issue I had is that sometimes TB lags ... and is unresponsive for a few seconds)... and that I miss betterbird :/
I created a new profile with all accounts: The error does not occur ... (However the profile is barebone without all the customizings I did in my profile ... ) Maybe the next BB Version ( also 128.5.1 as TB) will work too with the "normal" profile ... |
We're skipping 128.5.1, the reason is published. Things don't get magically fixed, but if it doesn't crash on a new profile, it's going to be even harder to track down. |
And TB runs on the BB profile or does it have its own profile? If it has its own profile, run it on the BB profile to see whether it crashes. |
I use the same profile in TB and BB |
The only thing we're aware of that is not 100% stable in BB is search in encrypted messages. But if that crashes, it's clearly linked to a user action. The other crash people complained about was related to the system tray under Gnome, but we worked around that. |
Encrypted Messages are heavily in use on my accounts (>30% are E2E encrypted with S/MIME ... some with PGP) ... I also use a lot of virtual Folders with Searches/Filters some with cascaded Search rules as they are supported with BB. I just tried disabling: "Enable search in encrypted messages (stores decrypted copy locally) " ... but it makes no difference is also crashing. |
That's for Gloda, it won't make any difference. Do any of those rules/filters/virtual folder search the body of the message? If so, disable that. |
Yes a lot of those rules/virtual folders search the body ... hope I captured all (will have to go through all rules once more) :
debug version :
|
Sorry, but this output isn't helpful. Are we chasing a crash in graphics or rule processing? This contains a clue (from a few comments up):
At least that shows that you're doing filtering with body search. Any body search on a PGP encrypted message may cause instability. That's because the search is written sync in C++, the PGP code is async JS and that may cause a problem. S/MIME is also written in C++ and won't cause an issue. You can check for body searches by looking through msgFilterRules.dat and virtualFolders.dat. |
How is this going? If it's down to filtering PGP encrypted messages, we may have to do some serious debugging in that area. |
I removed all body filters. However the crash continues. So I assume it is not about the encrypted messages. The crash also happens at the now actual version Betterbird 128.5.2esr-bb19. |
Maybe you can switch to FlatPak and follow its debugging instructions: I hope @mfschumann can assist. |
I installed the flatpak version: Created a new Profile. Copied all relevant stuff from the existing profile. It took very long but than I also got the crash:
Looks very much the same as the "normal" crash in BB ... I guess I have to wait ... maybe after an upgrade to the new kde version I will try again ... Strange that it does not happen in TB |
Hmm, libnspr4.so and libssl3.so is nothing we've tweaked. The crash you posted before in #380 (comment) was in libxul.so, which is Mozilla/TB/BB code. |
The error occurs only with Betterbird. It does not occur with Thunderbird 128.5.1 (same computer, os, profile, ... ). This error occurs after I switched from 115 to the 128.5.0 esr-bb18.en
OS: 22.04.1-Ubuntu
X11
No AV
Betterbird Version: Installed by unpacking : 'betterbird-128.5.0esr-bb18.en-US.linux-x86_64.tar.bz2'
Use is with 14 IMAP Mail Accounts; CalDav (4 Accounts);RSS Reader (deactivated), Chat deactivated
The error only occurs if Betterbird is switched to online. (about 10 seconds later when updating) If I start it with the profile option (Work offline) no error happens. The error also occurs in maintenance mode with all extensions disabled. If I switch to online the error happens. The only message I get is :
174610 Segmentation fault (core dumped)
3542086 Segmentation fault (core dumped)
3426479 Segmentation fault (core dumped)
308743 Segmentation fault (core dumped)
often combined with one or more stderr messages:
Exiting due to channel error.
Exiting due to channel error.
After I did a Repair folder (about 9000 Mails) the error happens in the update / download of the folder. Using Thunderbird with the same profile I was able to repair the folder and work normally.
The text was updated successfully, but these errors were encountered: