Summary: | Extremely verbose log spam from GUI component to xsession-errors | ||
---|---|---|---|
Product: | [Applications] kiten | Reporter: | Unknown <null> |
Component: | general | Assignee: | Joseph Kerian <jkerian> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexandre.bonneau, fbriere |
Priority: | NOR | ||
Version First Reported In: | 1.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Unknown
2016-03-20 07:44:29 UTC
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. |