Re: Turn off branch change detection as it leads to endless loop and CPU leak
Aleksey Midenkov <[email protected]> Thu, 26 Dec 2019 21:06:00 +0300
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <CAF8BazBy6xcSo8zy-56EjzpAARo3B_zO9CztGEs9aNVS6wqN_A@mail.gmail.com> |
On Wed, Dec 25, 2019 at 3:49 PM René J.V. Bertin <[email protected]> wrote: > On Wednesday December 25 2019 14:09:16 Aleksey Midenkov wrote: > > >change which happen quite frequently. So please, add an ability to turn > off > >branch change detection. > > Does this also happen when you change branches that do not have any > differences between them, i.e. when no files are being checked out? Does it > make a difference if you have the project configured to be parsed > completely on open or not? I don't know where it is configured. I use Custom Build System. Where is this option? > Do you use precompiled headers? Is it an option of KDevelop and where is it? Actually syntax parser is broken in several ways. Now it red-underlined lots of types in files (almost all or all of them) as syntax errors. I tried to jump from one of them and it jumped to the beginning of some random unrelated file and after that everything was fixed. All red "errors" was gone. I believe you don't test your software properly, do you? > > If what you describe comes in fact from reaction to bulk file changes then > there isn't much that can be done. You could add a feature to ignore file > changes for a predefined period or until further notice, but that too will > lead to incorrect parsing information for those files that did indeed > change. > > R. > -- All the best, Aleksey Midenkov @midenok