Comment # 2 on bug 1014999 from Nolan Leasy

- baloo is running prior to the KDE freeze, but does not seem to be the
problem:

~> balooctl status
Baloo File Indexer is running
Indexer state: Idle
Indexed 11 / 11 files
Current size of index is 140.00 KiB


- After freeze and CTL-ALT-F1, top processes in terms of CPU and memory are Web
Content and Firefox.

- Killing either the Web Content or Firefox processes (kill -9) and running
"init 5" from root gets me back to my LIGHTDM login, but then networking is not
functional after launching Plasma 5 -- this might be an unrelated issue, since
KDE was not restarted normally in this after-freeze case.

- Leaving the Web Content process running, I can't seem to get back to Plasma 5
without rebooting the machine.

- Logging in with GNOME, however, everything works normally, including
networking -- to reiterate, Leap 42.2 does not freeze at all running
GNOME/Cinnamon.

- This is happening on a Lenovo ThinkPad T400 (x86_64) -- I have been unwilling
to test on my primary laptop.

- The freeze sometimes does not take long when actively using the machine --
sometimes it takes longer -- other times it does not occur at all -- seems
random, but I'm sure there are a definite set of variables that have yet to be
identified -- it occurs frequently and unpredictably enough on this machine
that Leap 42.2/KDE is unusable. 

- I suspect a memory management issue of some sort, possibly involving both
Firefox and Plasma 5 -- but I have no proof at this point -- the behavior does
seem to be that of a piece of code stepping on display memory.

- Free memory on this machine is as follows and shows plenty available --
however this was taken when the machine was NOT freezing up:

~> free
             total       used       free     shared    buffers     cached
Mem:       1941732    1708548     233184     107428      59884     636192
-/+ buffers/cache:    1012472     929260
Swap:      2107388       1300    2106088