#
#asahi · 2024-10-29 23:36
charnam?
#asahi · 2024-10-29 23:36
PaulFertser_No, from the previous boot.
#asahi · 2024-10-29 23:35
PaulFertser_Post a link to a pastebin (any you like) containing your dmesg, yes.
#asahi · 2024-10-29 23:35
charnamthat likely wouldn't give you any information on my crashes since i don't believe any have happened since i've booted. would you still like me to do it?
#asahi · 2024-10-29 23:35
PaulFertser_You can even just do something like "sudo dmesg | nc termbin.com 9999"
#asahi · 2024-10-29 23:34
charnamor
#asahi · 2024-10-29 23:34
charnamyou want me to post the output of dmesg?
#asahi · 2024-10-29 23:34
PaulFertser_dmesg
#asahi · 2024-10-29 23:34
charnami'm not sure how to do that
#asahi · 2024-10-29 23:31
PaulFertser_Do you also get OOM with kernel-level allocation of order=0?
#asahi · 2024-10-29 23:30
PaulFertser_Full OOM kernel messages contains all the information about userspace processes and the amount of memory they used, no need for top or other ways of monitoring memory usage really, full kernel log should be enough.
#asahi · 2024-10-29 23:30
charnamPaulFertser_: interesting. maybe it's related, hopefully it gets looked into
#asahi · 2024-10-29 23:29
charnamjawmare: i could also use top, but it's just inconvenient since it's not going to stay on my screen unless i put it on top, and then it's taking up more screen space than it should
#asahi · 2024-10-29 23:28
PaulFertser_https://social.treehouse.systems/@marcan/113255100055208143
#asahi · 2024-10-29 23:27
PaulFertser_There's also an issue where OOM does something nobody can explain yet, without any apparent memory pressure and with enough swap...
#asahi · 2024-10-29 23:27
jawmareor you can use top to monitor memory usage
#asahi · 2024-10-29 23:27
charnamand yeah, now i can see i'm using a little bit more memory than i should be. that's probably why i'd never encountered this issue before, honestly
#asahi · 2024-10-29 23:26
charnami click on the memory usage widget and plasmashell crashes, that's great
#asahi · 2024-10-29 23:25
charnaminteresting, i can try to put it back in that case. i just removed all of the monitors since none were working
#asahi · 2024-10-29 23:24
jawmareim not 100% but the memory usage readout should be correct
#asahi · 2024-10-29 23:23
charnamlol
#asahi · 2024-10-29 23:23
charnamwell unfortunately i can't see my memory usage anymore because of ksystemstats not working anymore
#asahi · 2024-10-29 23:23
jawmarethere is something spooky going on, either its firefox memory leak, or somehow oom killer too eager to kill processes
#asahi · 2024-10-29 23:22
charnami mean, i've never had this issue before, and i've been able to open several instances of different applications without (too many) problems
#asahi · 2024-10-29 23:21
charnamwould a swap file fix this, or is kernel a more severe thing?
#asahi · 2024-10-29 23:20
jawmareyeah thats kernel oom killer kicking in
#asahi · 2024-10-29 23:18
charnamnot sure how to tell but i'm seeing phrases like "IOCTL" "Cannot allocate enough memory (handle=...)" -- would this be kernel?
#asahi · 2024-10-29 23:18
jawmareis it systemd oom or kernel oom?
#asahi · 2024-10-29 23:17
charnamand i know that because of the picture i took. is that all the information needed?
#asahi · 2024-10-29 23:17
charnamyes
#asahi · 2024-10-29 23:17
jawmareits oom
#asahi · 2024-10-29 23:16
charnamoh, also, when firefox crashed, it also closed chromium, which i had open at the same time. if i ran it in konsole and got it to crash, konsole would close as well
#asahi · 2024-10-29 23:15
charnami can type out the errors i saw here. i took pictures of it but i wasn't able to copy the text (since it was in a TTY) and i don't feel like getting the error to happen again. should i just type that here, or in a paste service? can't share the pictures themselves for privacy reasons
#asahi · 2024-10-29 23:15
jawmareanyways, lets move on to firefox
#asahi · 2024-10-29 23:14
jawmare(I like it more than the new system monitor)
#asahi · 2024-10-29 23:13
jawmarediffernt backend
#asahi · 2024-10-29 23:13
jawmareplasma 5 uses ksysguard
#asahi · 2024-10-29 23:13
charnamor, to be more specific, a newer version of Asahi
#asahi · 2024-10-29 23:13
charnambut they both started happening after i upgraded to plasma 6
#asahi · 2024-10-29 23:13
charnamwell in that case, they're probably unrelated
#asahi · 2024-10-29 23:13
charnaminteresting
#asahi · 2024-10-29 23:12
jawmarehttps://bugs.kde.org/show_bug.cgi?id=493093 https://bugs.kde.org/show_bug.cgi?id=495524
#asahi · 2024-10-29 23:12
charnamsimilar crashes? or what
#asahi · 2024-10-29 23:12
jawmareyeah, right before you joined
#asahi · 2024-10-29 23:12
charnamoh, really?
#asahi · 2024-10-29 23:11
jawmarewe were just talking about ksystemstats
#asahi · 2024-10-29 23:10
charnams/memory issues/memory allocation issues
#asahi · 2024-10-29 23:09
charnamit gave me some things about memory issues. i don't believe it would be the computer itself's fault, but i'm not opposed to testing that, since nobody else here seems to have even heard of this issue
#asahi · 2024-10-29 23:09
charnamnow, i've tried starting a plasma session, starting firefox from a TTY, and then looking in the tty console for whatever errors appear when firefox crashes. i'm usually able to get it to do that by zooming in, under certain circumstances
#asahi · 2024-10-29 23:08
charnambasically, applications on my system were randomly crashing, as well as ksystemstats creating at least 10 notifications as i logged in after upgrading my system to the newest version

plus ›