Version: 1.7 (using KDE KDE 3.3.0) Installed from: Gentoo Packages Compiler: 3.x OS: Linux It's unusable and so is the whole system, so I marked as "crash". I don't know why it is doing this. First I opened Kile 1.7 for the first time. It opened up my previously-opened projects. I finally managed to close them, during which I had the 100% CPU problem. I restarted and I still have the problem.
Jeroen, I fixed it. I set autosave=false instead of true in kilerc and that fixed it. Not sure why, but Kile was trying to autosave A LOT. So many times in one second that it's hard even to count.... But let's leave this bug open and call it a "autosave goes crazy when upgrading from 1.6.3 to 1.7". I don't know if it's specific to people upgrading, as I haven't tried starting with a fresh kilerc profile and created a project from scratch. I'm not at home now (I'm over VNC) so I can't check all this easily right now.
This may in fact be an upgrade issue. After fixing the autosave and changing it to false manually, I loaded kile, and then changed the autosave option in the Options, setting it to 5 minutes. It now works fine.
On Wednesday 15 September 2004 20:04, David Grant wrote: > ------- This may in fact be an upgrade issue. After fixing the autosave > and changing it to false manually, I loaded kile, and then changed the > autosave option in the Options, setting it to 5 minutes. It now works > fine. A ha, I remember. Kile sets an autosave timer in mili-seconds, however in kile-1.6.x it was saved in minutes. In kile-1.7 for some good (but I might change my mind) reason it was saved in ms as well. I did wrote a conversion program that should run automatically, evidently it didn't. This cause your autosave time to be set to 5 ms, which is too often even for paranoid persons like me. Thanks for the info, I will try to fix it. best, Jeroen
Can you perhaps perform a check for me? (As usual it turns out to be trickier than I thought.) In $HOME/.kde/share/config there is a file kconf_updaterc, there should be a section about kile in there. Perhaps you can attach the file here, or search the file for the word kile and post the relevant section. thanks, Jeroen
Jeroen, I can't see the word kile anywhere in that file.
Ok, that's no good. It probably means kupdate_conf did not run. best, Jeroen
Did you try 1.8b2, does the problem still occur? best, Jeroen
Please reopen if the problem occurs with 1.8 as well. best, Jeroen