Version: 1.7b2 (using KDE 3.3.1, SuSE) Compiler: gcc version 3.3.3 (SuSE Linux) OS: Linux (i686) release 2.6.9 Sometimes kile hangs (gui freeze) and nothing can be done (no save documents, etc). cpu usage is very low (< 2%). Only killing kile helps.
Version: 1.8.1 (KDE 3.4.2, debian testing) Compiler: unkown Os: Linux (i686) 2.6.13 I have the same problem. The GUI hangs and I can nothing do. There is no CPU usage (<1%). I started kile from a console and after this problem happend, I noticed this there: ----8<--------8<--------8<--------8<--------8<---- X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00df8 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00df8 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 18 Minor opcode: 0 Resource id: 0x2a00df8 ----8<--------8<--------8<--------8<--------8<---- Then I killed kile and restarted it. Is there a signal that I could send kile that it saves my work? Something like SIGUSR1? Thanks Chris
This doesn't look like a Kile bug, but worse. If you wait long enough (i.e. minutes), does that help?
*** Bug 114006 has been marked as a duplicate of this bug. ***
I'm having the same problem. It seems that the GUI freezes while kile does an autosave of the document i'm typing in. I find the active document correctly saved at the time the GUI freezed. AND I find the .backup file saved at the same time. The content of both files is identical. The other documents remain unsaved until the next autosave is scheduled (10 Minutes later for me). When I log out of KDE before all documents in Kile are autosaved. I can choose wether i want to save these documents or not. Hope this helps... It's not a good feeling having an editor that freezes from time to time while writing ur thesis =) Cheers, Christopher
Same thing happened to me twice today; I'm attaching the backtrace. It seems like the enter_loop hack in KIO::NetAccess might be the culprit, although I don't quite understand why it doesn't exit the eventloop in this particular case. I'm tempted to think though, that something like the attached patch might "fix" it, but it's hard to test with a not-really-reproducible hang like this.
Created attachment 13244 [details] backtrace
Created attachment 13245 [details] tentative patch
Hi, thanks for the patch. I actually managed to reproduce the bug, so that is good news. The bad news is that your patch didn't fix the bug. However, I'm working on a different solution that looks promising. best, Jeroen
Fixed the bug for the next release (kile 1.9). If you are able, please test it, to make sure the bug is really gone. best, Jeroen