Re: Okular locked up my system and left no evidence

2023-05-02 Thread Borden
10 Feb 2023, 10:53 by didi.deb...@cknow.org: > On Friday, 10 February 2023 07:46:36 CET Borden wrote: > >> which may be more productive. >> > > What would be even more productive is the following: > - log in remotely before doing another test and open a screen/tmux session > (or > open

Re: Okular locked up my system and left no evidence

2023-02-10 Thread Diederik de Haas
On Friday, 10 February 2023 07:46:36 CET Borden wrote: > which may be more productive. What would be even more productive is the following: - log in remotely before doing another test and open a screen/tmux session (or open several distinct remote logins) and start: - htop - tail -f

Re: Okular locked up my system and left no evidence

2023-02-10 Thread Alex DEKKER
On 10/02/2023 06:46, Borden wrote: There's a grave problem with how Okular processes PDF forms. Simple, short-answer text entry has ballooned a simple 1 MB file into a 1.2 GB file. This would explain (but not excuse) the excessive CPU and hard-drive usage. It probably also maxed out the RAM

Re: Okular locked up my system and left no evidence

2023-02-09 Thread Borden
10 Feb 2023, 01:03 by borde...@tutanota.com: > I was trying to fill out a PDF form on Okular and my system started crawling > to halt on text fields until it locked up completely. SSD stayed solid on (so > God knows how many write cycles it gluttoned), fan went into overdrive trying > to keep

Okular locked up my system and left no evidence

2023-02-09 Thread Borden
I was trying to fill out a PDF form on Okular and my system started crawling to halt on text fields until it locked up completely. SSD stayed solid on (so God knows how many write cycles it gluttoned), fan went into overdrive trying to keep the circuitry from frying, and the computer