Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Firefox and Chromium keep crashing (Read 3953 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: Firefox and Chromium keep crashing

Reply #31 –
Quote from: ####### – on
I like BTRFS and use it whenever possible.
Code: [Select]
# btrfs scrub start /
# btrfs scrub status /
scrub is used on a mounted system and if there are any problems it will tell you including the paths of any affected files, fsck on ext4 just gives you inode numbers last I saw, which was a few years ago now!
Thinking about a segmentation fault though, you usually get that from say writing too much data into a fixed size variable, it's a memory related problem from accessing an incorrect memory address. If it isn't hw then possibly it could be some hw specific memory management bug, so using the lts version or even some older pre - March version you used successfully before to check as occasionally things get backported to lts might be worth trying.
Sometimes the BIOS menus have memory check features, they might take an hour or two to run.


This scrub?  https://aur.archlinux.org/packages/scrub 

Package Details: scrub 2.6.1-1
Git Clone URL:   https://aur.archlinux.org/scrub.git (read-only, click to copy)
Package Base:   scrub
Description:   Iteratively writes patterns on files or disk devices to make retreiving the data more difficult
Upstream URL:   http://code.google.com/p/diskscrub/
Cat Herders of Linux

Re: Firefox and Chromium keep crashing

Reply #32 –
Quote from: tintin – on
I assume you have a swap partition?
No I don't.

Quote from: ####### – on
I like BTRFS and use it whenever possible.
Code: [Select]
# btrfs scrub start /
# btrfs scrub status /
scrub is used on a mounted system and if there are any problems it will tell you including the paths of any affected files, fsck on ext4 just gives you inode numbers last I saw, which was a few years ago now!
Thinking about a segmentation fault though, you usually get that from say writing too much data into a fixed size variable, it's a memory related problem from accessing an incorrect memory address. If it isn't hw then possibly it could be some hw specific memory management bug, so using the lts version or even some older pre - March version you used successfully before to check as occasionally things get backported to lts might be worth trying.
Sometimes the BIOS menus have memory check features, they might take an hour or two to run.
I tried it and I got 10 errors. It didn't give me any path but I looked through dmesg and looks like there are some cheksum errors on some files:
Code: [Select]
[12509.529649] BTRFS info (device dm-0): scrub: started on devid 1
[12609.109367] BTRFS warning (device dm-0): checksum error at logical 15383490560 on dev /dev/mapper/cryptroot, physical 16465620992, root 257, inode 848039, offset 3313664, length 4096, links 1 (path: lorenzo/Music/林慧萍46张无损专辑/2002-06-可以勇敢可以温柔典藏精选 2CD[引进版][WAV]/林慧萍.-.[可以勇敢可以温柔典藏精选CD2勇敢篇](2002)[WAV]/林慧萍.-.[可以勇敢可以温柔典藏精选CD2勇敢篇](2002)[WAV].wav)
[12609.109397] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 62, gen 0
[12609.109406] BTRFS error (device dm-0): unable to fixup (regular) error at logical 15383490560 on dev /dev/mapper/cryptroot
[12609.164467] BTRFS warning (device dm-0): checksum error at logical 15383494656 on dev /dev/mapper/cryptroot, physical 16465625088, root 257, inode 848039, offset 3317760, length 4096, links 1 (path: lorenzo/Music/林慧萍46张无损专辑/2002-06-可以勇敢可以温柔典藏精选 2CD[引进版][WAV]/林慧萍.-.[可以勇敢可以温柔典藏精选CD2勇敢篇](2002)[WAV]/林慧萍.-.[可以勇敢可以温柔典藏精选CD2勇敢篇](2002)[WAV].wav)
[12609.164474] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 63, gen 0
[12609.164476] BTRFS error (device dm-0): unable to fixup (regular) error at logical 15383494656 on dev /dev/mapper/cryptroot
[12635.738759] BTRFS warning (device dm-0): checksum error at logical 20031221760 on dev /dev/mapper/cryptroot, physical 21113352192, root 257, inode 848106, offset 97746944, length 4096, links 1 (path: lorenzo/Music/林慧萍46张无损专辑/1994-04-梦醒·心碎·空叹息[点将][WAV]/林慧萍.-.[梦醒心碎空叹息](1994)[WAV].wav)
[12635.738767] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 64, gen 0
[12635.738780] BTRFS error (device dm-0): unable to fixup (regular) error at logical 20031221760 on dev /dev/mapper/cryptroot
[12635.882613] BTRFS warning (device dm-0): checksum error at logical 20031225856 on dev /dev/mapper/cryptroot, physical 21113356288, root 257, inode 848106, offset 97751040, length 4096, links 1 (path: lorenzo/Music/林慧萍46张无损专辑/1994-04-梦醒·心碎·空叹息[点将][WAV]/林慧萍.-.[梦醒心碎空叹息](1994)[WAV].wav)
[12635.882620] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 65, gen 0
[12635.882622] BTRFS error (device dm-0): unable to fixup (regular) error at logical 20031225856 on dev /dev/mapper/cryptroot
[12685.759826] BTRFS warning (device dm-0): checksum error at logical 28313563136 on dev /dev/mapper/cryptroot, physical 29395693568, root 257, inode 848256, offset 440688640, length 4096, links 1 (path: lorenzo/Music/林慧萍46张无损专辑/1995-05-风吹草动[点将][WAV]/林慧萍.-.[风吹草动](1995)[WAV].wav)
[12685.759844] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 66, gen 0
[12685.759847] BTRFS error (device dm-0): unable to fixup (regular) error at logical 28313563136 on dev /dev/mapper/cryptroot
[12685.775051] BTRFS warning (device dm-0): checksum error at logical 28313567232 on dev /dev/mapper/cryptroot, physical 29395697664, root 257, inode 848256, offset 440692736, length 4096, links 1 (path: lorenzo/Music/林慧萍46张无损专辑/1995-05-风吹草动[点将][WAV]/林慧萍.-.[风吹草动](1995)[WAV].wav)
[12685.775058] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 67, gen 0
[12685.775060] BTRFS error (device dm-0): unable to fixup (regular) error at logical 28313567232 on dev /dev/mapper/cryptroot
[12792.452604] BTRFS warning (device dm-0): checksum error at logical 47382147072 on dev /dev/mapper/cryptroot, physical 48464277504, root 256, inode 494606, offset 131072, length 4096, links 1 (path: usr/lib32/wine/i386-unix/d3d9.dll.so)
[12792.452641] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 68, gen 0
[12792.452656] BTRFS error (device dm-0): unable to fixup (regular) error at logical 47382147072 on dev /dev/mapper/cryptroot
[12792.501022] BTRFS warning (device dm-0): checksum error at logical 47382151168 on dev /dev/mapper/cryptroot, physical 48464281600, root 256, inode 494606, offset 131072, length 4096, links 1 (path: usr/lib32/wine/i386-unix/d3d9.dll.so)
[12792.501039] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 69, gen 0
[12792.501041] BTRFS error (device dm-0): unable to fixup (regular) error at logical 47382151168 on dev /dev/mapper/cryptroot
[12792.546625] BTRFS warning (device dm-0): checksum error at logical 47382155264 on dev /dev/mapper/cryptroot, physical 48464285696, root 256, inode 494606, offset 131072, length 4096, links 1 (path: usr/lib32/wine/i386-unix/d3d9.dll.so)
[12792.546632] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 70, gen 0
[12792.546635] BTRFS error (device dm-0): unable to fixup (regular) error at logical 47382155264 on dev /dev/mapper/cryptroot
[12792.586296] BTRFS warning (device dm-0): checksum error at logical 47382159360 on dev /dev/mapper/cryptroot, physical 48464289792, root 256, inode 494606, offset 131072, length 4096, links 1 (path: usr/lib32/wine/i386-unix/d3d9.dll.so)
[12792.586303] BTRFS error (device dm-0): bdev /dev/mapper/cryptroot errs: wr 0, rd 0, flush 0, corrupt 71, gen 0
[12792.586306] BTRFS error (device dm-0): unable to fixup (regular) error at logical 47382159360 on dev /dev/mapper/cryptroot
[13020.293505] BTRFS info (device dm-0): scrub: finished on devid 1 with status: 0
I don't know why those file should be problematic, but I doubt it's the reason for the crashes.

Re: Firefox and Chromium keep crashing

Reply #33 –
I guess you have a luks encrypted partition on /dev/mapper/cryptroot and it sounds like there are filesystem errors on that whatever it is, although I haven't tried btrfs scrub with encryption myself, so I don't know if that is the case for certain. The only time I found errors like that though was on a USB formatted to BTRFS and replacing the problem files didn't work because more things got corrupted later as the USB had gone faulty, so it could mean you have a drive going bad, whatever drive that /dev/mapper/cryptroot refers to. Take a look at some of those files it mentions like those .wav ones and see if they really are corrupted and don't play properly, compare the system files to good examples from somewhere else by md5sum or something, that should give more confirmation if the drive is really mangling the data on it.

Re: Firefox and Chromium keep crashing

Reply #34 –
The .wav files play perfectly fine.

Yesterday another strange phenomenon happened. I was watching a video with mpv and suddenly all the running programs that use GTK closed by themselves, which are: Thunar, Thunderbird, Clipit and Nicotine+. After that the mpv video's audio stopped and the playback started to lag. I can tell that only GTK programs crashed as qBittorrent, KeePassXC and Anki haven't been affected (even if I had a Segmentation Fault error before with Anki as I said in another post). When I reopened Thunar its configurations were gone (for example the "Show hidden files" option was unchecked, even if I configured it before). When I restarted the computer it was back to normal.

I'll try Linux LTS as suggested and see if it's a kernel problem. If it is not, I'll try that filesystem check from a live session and see if I can find out something. Otherwise I'll try to format and reinstall the system with ext4 instead of btrfs to see if it's a filesystem problem. If nothing changes I'll try to install the system on another hard drive.

Re: Firefox and Chromium keep crashing

Reply #35 –
Sounds like a good plan.  Sorry for your troubles.  Even a small 1-2 gb swapfile could benefit your system if the hdd is stable and running properly.
Cat Herders of Linux

Re: Firefox and Chromium keep crashing

Reply #36 –
Turned out that one of my RAM bank was damaged. I run a test with memtest86 and it returned a lot of errors. I replaced it with another bank and now everything is working fine. I should have done this test sooner...
Thanks to everyone who contributed to this thread!

Re: [SOLVED] Firefox and Chromium keep crashing

Reply #37 –
Glad it wasn't a catastrophic loss.   A mem stick isn't so bad.  Sorry you had such troubles.  Happy it's all working now!
Cat Herders of Linux