Summary: | Kate freezes when trying to open any file using the File->Open menu command. | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Ekkehard Blanz <Ekkehard.Blanz> |
Component: | application | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | christoph, dl, kukarzev, Matthieu.Stigler |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ekkehard Blanz
2012-05-09 20:18:53 UTC
I individually reset all of the "Configure Kate... Settings" and this problem went away. Still something you might want to look into, albeit with low priority. I'm still willing to help, however, not sure how much I can do now that the problem doesn't show itself anymore. I confirm this bug on Ubuntu 12.04 64 bits, using KDE 4.8.4. The bug is not only present with Kate 3.8.4, but also with other KDE-based applications such as rkward (I think based/using itself on kate). It is difficult ot understand what triggers the bug. It does not happen immediately, but once it happens, it happens each time. The only solution found was to reset settings, with $mv ./kde ./kde-old Please let me know if any input can be provided. Confirm the problem - running 64 bit Ubuntu 12.04 and Kate 4.8.4 After a while - with longer editing sessions and just a few files (about 10) it will start getting slow on file open and eventually freeze. Resetting by removing the .kde directory does not seem to help. Although logging out and back in again does. This suggests that the problem is a memory leak not a settings issue. Could you try to look which other processes are running? Does some kded or Co. run around with massive cpu time or memory usage? On Tuesday, October 30, 2012 12:38:02 PM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=299706
>
> Christoph Cullmann <cullmann@kde.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |cullmann@kde.org
>
> --- Comment #4 from Christoph Cullmann <cullmann@kde.org> ---
> Could you try to look which other processes are running? Does some kded or
> Co. run around with massive cpu time or memory usage?
Pretty sure that wasn't happening at the time, since there are a few culprits
as we know in dbus and akonadi land that tend to do that, so I am constantly
monitoring cpu use in all 6 cores and would have noticed if this was
happening.
But as for this particular bug, I couldn't reproduce it ever for the last
couple of months (and I am using the system including kate 10+ hours daily).
Not sure which update made it disappear. So since I can't reproduce it (and
you probably can't either), I guess we should close it.
Cheers
Ekkehard
Ok, if it reoccurs and you can give us any hints, please reopen ;) Thanks for your investigations. I had this or very similar issue, and in my case the culprit was a nonexistent NFS mount: I had an entry for it in fstab, for an NFS disk at home, and at work it was not available. Once I removed the fstab entry and rebooted, the open file dialog worked as it should, no freezes. |