Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
Something wrong in your steps... Below detail On Mon, Jul 05, 2010 at 08:01:57PM +0300, Fathi Boudra wrote: Using your recomendation I remove that dir and config. But this is not help. While next background job is starting i had the same problem. Project is available, this is rtmpd.com - OpenSource project. When I import clean project(just svn'ed) in kdevelop4 all is fine. Project indexing(via background job) pass successful.After this i run cmake . make (on builders/cmake directory) next background job leads to eating memory and hard CPU usage. I think this happend cause project generate several sym-lynks to upper directories - got several loops of scanning. I'm not able to reproduce so far. Maybe there's a difference on the way the project is created. Could you send the exact step you do and your kdevelop project file ? my steps: - get crtmpserver 0.1 branch (r1421) - run kdevelop - project - open/import project... - select crtmpserver/builders/cmake/CMakeLists.txt - set project name to crtmpserver - set build directory to crtmpserver/build This is ugly thing, but with kdevelop you can not to set build directory as crtmpserver/builders/cmake, but this is need to correct building. In easy way you can change config manually. Edit crtmpserver/builders/cmake/.kdev4/cmake.kdev4 and set builders/cmake as build dir. This is variables: CurrentBuildDir BuildDirs Also add [Launch][Launch Configuration 0][Data] Arguments=rtmpserver/rtmpserver.lua In another way you can build via pure console: in crtmpserver/builders/cmake run cmake . make After build run kdevelop on with this project. - ok - project - build all projects - it fails to build on vmtests - close project - close kdevelop - run kdevelop - project - open recent - select crtmpserver project -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706095358.gc5...@img.jet.kiev.ua
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
This is ugly thing, but with kdevelop you can not to set build directory as crtmpserver/builders/cmake, but this is need to correct building. Why should I do that ? I should be able to set build directory as I want and not specifically crtmpserver/builders/cmake. In easy way you can change config manually. Edit crtmpserver/builders/cmake/.kdev4/cmake.kdev4 and set builders/cmake as build dir. This is variables: CurrentBuildDir BuildDirs Also add [Launch][Launch Configuration 0][Data] Arguments=rtmpserver/rtmpserver.lua In another way you can build via pure console: in crtmpserver/builders/cmake run cmake . make After build run kdevelop on with this project. This is the way you reproduce the endless loop ? I mean: import the project with kdevelop, close kdevelop and edit kdevelop project files. Please, give me complete and exact steps to reproduce. By the way, it seems an upstream bug and not a Debian packaging bug. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktintu6ksw9w_iimvygxff4qlvefpedllg-jlr...@mail.gmail.com
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
On Tue, Jul 06, 2010 at 02:56:29PM +0300, Fathi Boudra wrote: This is ugly thing, but with kdevelop you can not to set build directory as crtmpserver/builders/cmake, but this is need to correct building. Why should I do that ? I should be able to set build directory as I want and not specifically crtmpserver/builders/cmake. In easy way you can change config manually. Edit crtmpserver/builders/cmake/.kdev4/cmake.kdev4 and set builders/cmake as build dir. This is variables: CurrentBuildDir BuildDirs Also add [Launch][Launch Configuration 0][Data] Arguments=rtmpserver/rtmpserver.lua In another way you can build via pure console: in crtmpserver/builders/cmake run cmake . make After build run kdevelop on with this project. This is the way you reproduce the endless loop ? I mean: import the project with kdevelop, close kdevelop and edit kdevelop project files. Main target to do this step is get buggy environment. Problem is reveal while background jobs working on previosly cmakemake'ed source tree. No matter which way we receive environment(clean console or kdevelop). Please, give me complete and exact steps to reproduce. 1. get sources 2. cd builders/cmake 3. cmake . make 4. run Kdevelop4 5. import cmake project from builders/cmake 6. open some source files (for running background jobs, i think this is indexing of source files for highlight and code completion) By the way, it seems an upstream bug and not a Debian packaging bug. This bug is revealed after everyday updates. As I can saw, that update consist of Qt libraries update, but not kdevelop. I'm sorry for foggy bug report, I'm novice :) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100706145508.gd5...@img.jet.kiev.ua
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
Hi, Is your cmake based project available somewhere ? try to remove ~/.kdevduchain directory and test if it's better. Cheers, Fathi -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin_kbgslh4x7jc6rsmypvceevuokwhcdtfr8...@mail.gmail.com
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
On Mon, Jul 05, 2010 at 02:59:08PM +0300, Fathi Boudra wrote: Is your cmake based project available somewhere ? try to remove ~/.kdevduchain directory and test if it's better. remove also ~/.kde/share/config/kdeveloprc (or rename to kdeveloprc.backup) I'm sorry, i had mistake. Mistake about sym-links. I made rash assumption. But problem is still actual. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100705140050.gb5...@img.jet.kiev.ua
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
On Mon, Jul 05, 2010 at 02:59:08PM +0300, Fathi Boudra wrote: Is your cmake based project available somewhere ? try to remove ~/.kdevduchain directory and test if it's better. remove also ~/.kde/share/config/kdeveloprc (or rename to kdeveloprc.backup) Using your recomendation I remove that dir and config. But this is not help. While next background job is starting i had the same problem. Project is available, this is rtmpd.com - OpenSource project. When I import clean project(just svn'ed) in kdevelop4 all is fine. Project indexing(via background job) pass successful.After this i run cmake . make (on builders/cmake directory) next background job leads to eating memory and hard CPU usage. I think this happend cause project generate several sym-lynks to upper directories - got several loops of scanning. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100705135223.ga5...@img.jet.kiev.ua
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
Using your recomendation I remove that dir and config. But this is not help. While next background job is starting i had the same problem. Project is available, this is rtmpd.com - OpenSource project. When I import clean project(just svn'ed) in kdevelop4 all is fine. Project indexing(via background job) pass successful.After this i run cmake . make (on builders/cmake directory) next background job leads to eating memory and hard CPU usage. I think this happend cause project generate several sym-lynks to upper directories - got several loops of scanning. I'm not able to reproduce so far. Maybe there's a difference on the way the project is created. Could you send the exact step you do and your kdevelop project file ? my steps: - get crtmpserver 0.1 branch (r1421) - run kdevelop - project - open/import project... - select crtmpserver/builders/cmake/CMakeLists.txt - set project name to crtmpserver - set build directory to crtmpserver/build - ok - project - build all projects - it fails to build on vmtests - close project - close kdevelop - run kdevelop - project - open recent - select crtmpserver project -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikqjnbp5rx2ycccfx9dcbod-9x2uqtozzcfi...@mail.gmail.com
Bug#587502: kdevelop: Regression. Too many resources is used while doing background jobs.
Package: kdevelop Version: 4:4.0.0-2.1 Severity: critical Tags: squeeze Justification: breaks unrelated software About week ago I had several minor updates in Qt libs. After this update background jobs is eating all recources of my PC(I have AMD Athlon(tm) 64 X2 5200+, 1,8G RAM). While this problem is happend, kdevelop use all available RAM, after than it use big piece if swap. During this time i see strong hard disk activity. Step to reproduce: Import some CMake based project Wait until start background jobs(I think this is project sources indexing) Look for RAM/HDD usage and activity. Also I would say project tree have cross symlinks inside. Also as I can see kdevelop can not eat more than 1,8-2G RAM (I see this on another PC with Intel C2D, 4G RAM inside) If you need additional info I'm ready to answer. P.S. kdevelop and kdevplatform version .1 is only recompiled sources available via deb-src repo(using apt-get source + dpkg-buildpackage). But this has no effect, regression is still present. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (111, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdevelop depends on: ii kdebase-runtime 4:4.4.4-1 runtime components from the offici ii kdevelop-data4:4.0.0-2.1 data files for the KDevelop IDE ii kdevplatform1-libs 1.0.0-1.1 shared libraries for the KDevelop ii lcov 1.8-1.1 Summarise Code coverage informatio ii libc62.11.1-3Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-5 GCC support library ii libkdecore5 4:4.4.4-2 the KDE Platform Core Library ii libkdeui54:4.4.4-2 the KDE Platform User Interface Li ii libkio5 4:4.4.4-2 the Network-enabled File Managemen ii libkparts4 4:4.4.4-2 the Framework for the KDE Platform ii libktexteditor4 4:4.4.4-2 the KTextEditor interfaces for the ii libprocessui4a 4:4.4.4-1 library for ksysguard process user ii libqt4-dbus 4:4.6.3-1 Qt 4 D-Bus module ii libqt4-help 4:4.6.3-1 Qt 4 help module ii libqt4-network 4:4.6.3-1 Qt 4 network module ii libqt4-script4:4.6.3-1 Qt 4 script module ii libqt4-webkit4:4.6.3-1 Qt 4 WebKit module ii libqtcore4 4:4.6.3-1 Qt 4 core module ii libqtgui44:4.6.3-1 Qt 4 GUI module ii libstdc++6 4.4.4-5 The GNU Standard C++ Library v3 ii libsublime1 1.0.0-1.1 an user interface library ii libthreadweaver4 4:4.4.4-2 the ThreadWeaver Library for the K Versions of packages kdevelop recommends: ii gdb 7.0.1-2The GNU Debugger ii valgrind 1:3.5.0-3 A memory debugger and profiler Versions of packages kdevelop suggests: ii cmake 2.8.1-5A cross-platform, open-source make ii kdevelop-l10n-uk [kdevelop-l1 4:4.0.0-2 Ukrainian (uk) localization files -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629100412.14534.60802.report...@fame.in-ring.net
