3 ms·
Each of the >30 times I've hit F5 on this site in Chromium it causes a 100% reproducible, complete tab crash. The tab fully loads and appears properly for abou
by exikyut 8y ago
Each of the >30 times I've hit F5 on this site in Chromium it causes a 100% reproducible, complete tab crash.
The tab fully loads and appears properly for about... 100ms or so beforehand, so I'm pretty sure it's to do with some kind of wasm interaction. I have my microphone set to "ask before accessing" so I don't think the crash is to do with audio.
FWIW, I've been experiencing periodic tab crashes for the past few weeks, and need to do a package upgrade to move up from 68.0, so this may not be interesting to anybody.
But in case someone sees this and wants to chase it down, let me know; debugging Chromium can be fun. Unfortunately Arch doesn't provide debug symbols for their builds :'( so that's a bit of a setback, but yeah.
- yjftsjthsd-h 8y agoWhy are you not up to date? Chrom/ium has a stable extension API; it's not like it should break anything, and you're missing security and bug fixes.
- exikyut 8y agoInsufficient diskspace, to be honest (avg. 50-100MB free on /). Which is due to expensive medical issues that make it tricky for me to work. Been a problem for a while - worked with just under 8MB free for two years on the 486 I used between 2003 and 2005. The reason I'm doing my best to sit still until I can fix things properly is that buying small HDDs a) multiplies single points of failure beyond the many, many disks I have boxed up and hope still work, and b) increases the total capacity I'll need to _re-purchase_ when I can finally assemble a ZFS pool. Right now, I have enough 400MB and 4GB, 10GB, 60GB, etc HDDs that I need about 10TB (!!!!) of temporary capacity to sanely deduplicate everything. I'll figure out a solution eventually.