[kdevelop] [Bug 373017] Background parser memory on large project

2017-11-30 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=373017

JDF  changed:

   What|Removed |Added

 CC||dage...@free.fr

--- Comment #2 from JDF  ---
The bug is still present (kdevelop 5.2.1). 
On a 16 cores CPU, when setting 16 cores, the parser will use all the available
memory (8GB + 16 GB swap) until it crashes.
Reducing the parser to 12 cores will not show up the problem on the above
architecture (the parser will tend to use up to 6GB or RAM and few GB of swap).
Can be interesting to set a maximum of memory usage along with a maximum number
of cores.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373017] Background parser memory on large project

2017-12-04 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=373017

--- Comment #5 from JDF  ---
Here below are some links that might be useful. It seems that prlimit and
timeout can be interesting.
If you know that you have let's say 16GB on the machine, and the user wants
that 8GB maximum will be used for parsing and that he wants 16 threads to do
the work, then only 512 MB will be given for each clang process.
That looks too easy, and since I'm not inside kdevelop code (and know nothing
about how clang is doing code parsing) I might be missing important things that
will kill these ideas...

But other solutions might exist:

https://github.com/valloric/youcompleteme/issues/184

https://bugreports.qt.io/browse/QTCREATORBUG-11640

https://unix.stackexchange.com/questions/44985/limit-memory-usage-for-a-single-linux-process

https://unix.stackexchange.com/questions/1424/is-there-a-way-to-limit-the-amount-of-memory-a-particular-process-can-use-in-uni

https://letitknow.wordpress.com/2014/12/11/how-to-limit-memory-usage-of-a-process-under-linux/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402826] New: Code recognition does not work all the time

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402826

Bug ID: 402826
   Summary: Code recognition does not work all the time
   Product: kdevelop
   Version: 5.3.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: All editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jd.fratt...@free.fr
  Target Milestone: ---

For big projects (here autotool project), when opening a file, everything
except basic C++ token could remain white. Hover the mouse does not show any
information about the word (object, function...). Sometimes only few words of
the all file will be recognized.
Reloading the file (F5 or right-click then reload on the file tab) will often
make the recognition to work again, but not all the time.

On Debian Linux Buster, Xfce, kdevelop 5.3.1 appImage.
This issue is redundant since most versions of kdevelop (all 4.x, all 5.x) and
probably even older ones.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402826] Code recognition does not work all the time

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402826

JDF  changed:

   What|Removed |Added

 CC||jd.fratt...@free.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402828] New: Quick outline navigator shows namespaces twcie

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402828

Bug ID: 402828
   Summary: Quick outline navigator shows namespaces twcie
   Product: kdevelop
   Version: 5.3.1
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: All editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jd.fratt...@free.fr
  Target Milestone: ---

The quick outline navigator shows namespaces twice.

If you have a header:

namespace a
{
namespace b
{
namespace c
{
struct s
{
  void f();
};
}
}
}

and in the source file:

namespace a
{
namespace b
{
namespace c
{
void s::f()
{
   // click here or place cursor here
}
}
}
}

Then the quick outline navigator will show: a::b::c::a::b::c::s::f()

On Debian Buster, Xfce, with kdevelop 5.3.1 AppImage.
This issue is redundant since many versions of kdevelop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402828] Quick outline navigator shows namespaces twcie

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402828

JDF  changed:

   What|Removed |Added

 CC||jd.fratt...@free.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402830] New: Autotool project full of dirty symbols in the project tree

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402830

Bug ID: 402830
   Summary: Autotool project full of dirty symbols in the project
tree
   Product: kdevelop
   Version: 5.3.1
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: file tree
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jd.fratt...@free.fr
  Target Milestone: ---

With autotools projects, the project tree is displaying many useless symbols
discovered in various makefiles. The project tree ends with many symbols like
cscope-list, distclean, dvi, html... which are polluting the tree.
Since filters are not saved in the kdevelop project file, these need to be done
on all platforms where kdevelop is installed for the same project.
Plus this is not easy to filter all these dirty symbols: should be block all
html files ? all uninstall files ? And what if such files are really inside the
project.

On Debian Buster, Xfce, with kdevelop 5.3.1 AppImage.
This issue is redundant since many versions of kdevelop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402830] Autotool project full of dirty symbols in the project tree

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402830

JDF  changed:

   What|Removed |Added

 CC||jd.fratt...@free.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402832] kdevelop hangs for 1 second every few minutes

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402832

JDF  changed:

   What|Removed |Added

 CC||jd.fratt...@free.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 402832] New: kdevelop hangs for 1 second every few minutes

2019-01-03 Thread JDF
https://bugs.kde.org/show_bug.cgi?id=402832

Bug ID: 402832
   Summary: kdevelop hangs for 1 second every few minutes
   Product: kdevelop
   Version: 5.3.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: All editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jd.fratt...@free.fr
  Target Milestone: ---

On kdevelop 5.3.1 (not present on 5.2, but was present seldom on some previous
versions), all the kdevelop hangs for 1 second every minutes or so.

On Debian Buster, Xfce, with kdevelop 5.3.1 AppImage.
This issue is redundant since many versions of kdevelop.

-- 
You are receiving this mail because:
You are watching all bug changes.