This affects kiten in version 1.3 using KDE Frameworks 5.19.0, and Qt 5.5.1 as reported in the Version dialog, but has been present for an unknown period of time. Running Kiten causes the xsession-errors file (or on systemd-enabled platforms, the user journal) to be spammed with messages like this, at a frequency of several messages per second for the entire time kiten is running. The messages seem to be unnecessarily verbose and meaningless as they do not indicate any sort of error or unusual condition. Reproducible: Always Steps to Reproduce: 1. Launch kiten 2. Tail xsession-errors 3. Observe these messages Actual Results: Observed log spam as such (on my systemd-based OS, messages are redirected to the journal), hence the timestamps: Mar 20 16:10:16 rinne kiten[21594]: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] 0 Mar 20 16:10:16 rinne kiten[21594]: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 ) Posit Mar 20 16:10:16 rinne kiten[21594]: [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Mar 20 16:10:16 rinne kiten[21594]: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] 0 Mar 20 16:10:16 rinne kiten[21594]: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 ) Posit Mar 20 16:10:14 rinne kiten[21594]: [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Mar 20 16:10:14 rinne kiten[21594]: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] 0 Mar 20 16:10:14 rinne kiten[21594]: Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 ) Posit Mar 20 16:10:14 rinne kiten[21594]: [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Expected Results: Expected to see only meaningful log messages, if any. The application is run under the DWM tiling window manager. Other components of the KDE application suite which I am also using: dolphin (15.12.3), okular (0.24.2), kbibtex (0.6) – do not have this issue.
I'm currently on Kubuntu 16.05 using the kubuntu-ppa backports (http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial). I do not have kiten installed, but I still have a 60 _millions_ line log with : 59484176 [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 59484177 59484178 Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 59484179 59484180 Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] 0 ...repeated over and over (the number at the start of the line in the line number shown in vim). Unfortunately, I have no way of knowing which app is causing that, since this log is pretty useless. The workaround so far : `echo '' > .xsession-errors` every few days. Also, that would explain why the plasmashell process is _always_ at 100% of one cpu core.
These messages were generated by KHTML (specifically, dom_selection.cpp). Would it be safe to assume that this issue was resolved by the transition to QTextBrowser[1] in 20.03.80? [1] https://commits.kde.org/kiten/b0266cb89d2333da4280778dea54f735834db99f
(In reply to Frédéric Brière from comment #2) > These messages were generated by KHTML (specifically, dom_selection.cpp). > > Would it be safe to assume that this issue was resolved by the transition to > QTextBrowser[1] in 20.03.80? > > [1] https://commits.kde.org/kiten/b0266cb89d2333da4280778dea54f735834db99f I cannot tell you if it's been the case exactly since then, but on kiten 20.08.3 I do no longer see this problem, and haven't done so in quite a while. As far as I am concernced, this can be marked as fix released in upstream.
Thanks for the update; changing status.