since a few months I've had a weird problem with xournal. Basically running xournal for some time will cause such a massive memory consumption (on documents with just one page, even!) that oom-killer goes ahead and makes other applications - or xournal - crash. To me it looks as if the memory is heavily fragmented. Attached you will find a sample output from dmesg after such a crash.
Okay, this crash could come from anywhere, and xournal isn't exactly showing high memory consumption. So why blame xournal? I got two reasons for this. The first and most important is that for the past half year I've had this problem, but *only* when running xournal. It hasn't appeared a single time when xournal was closed. And I use xournal very unregularily, it's not like it's open most of the time but I do use it 2-3 times a week still. And these crashes ONLY happen then.
Another reason is that when displaying memory consumption, e.g. using htop, xournal doesn't show much memory usage - but X does, it can really fill up my 2 GB of memory! When I close down xournal in time however, the memory consumption goes down to normal levels again. Closing any other applications doesn't result in that effect. So I'm pretty sure that this problem is caused by xournal. I can provide additional information if you tell me what to do.
I'm on Arch Linux, by the way. My WM is Xmonad, my graphics chip is Intel GMA 950 running the Intel driver. The Laptop is a Thinkpad X60 Tablet.
Log in to post a comment.