[kdevelop] [Bug 402301] Unable to select matched patterns after performing a replace in Find/Replace in Files view
https://bugs.kde.org/show_bug.cgi?id=402301 Martin Fuhrer changed: What|Removed |Added Version Fixed In||5.6.1 Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Martin Fuhrer --- Thanks for following up, Justin. KDevelop 5.6.1 is in fact working as expected - double-clicking a match in the "Find/Replace in Files" view brings up the relevant line in the text editor, both before and after performing the Replace operation. I'll mark the status as resolved/fixed as someone clearly modified the behaviour since I first reported. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 Martin Fuhrer changed: What|Removed |Added Attachment #105746|0 |1 is obsolete|| --- Comment #22 from Martin Fuhrer --- Created attachment 112098 --> https://bugs.kde.org/attachment.cgi?id=112098&action=edit Heaptrack file (PID 12200) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 --- Comment #23 from Martin Fuhrer --- Created attachment 112099 --> https://bugs.kde.org/attachment.cgi?id=112099&action=edit KDevelop log (PID 12200) First and last 1000 lines (full log is 45 MB) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 --- Comment #24 from Martin Fuhrer --- I have been testing the KDevelop 5.2.1 AppImage on Debian 7.8 (wheezy) for the last few weeks (our office is still using KDevelop 4.7.4, which runs great, albeit a bit slow with large projects, and it would be nice to move to the latest). For the most part, KDevelop 5.2.1 is runs along with no problems (sometimes for one to two days at a time), but occasionally it starts eating away at memory rapidly, to the point where my desktop starts freezing up and I have to type Ctrl-Alt-F1 to switch to console mode and kill the kdevelop process. My workstation has 32 GB RAM, and after I kill the process, usually 20 GB or more becomes available again. The last few days I have been launching KDevelop with the latest heaptrack (built from master). Rather than launching the AppRun script, I simply set the environment variables from my shell (csh), and launch KDevelop with: heaptrack kdevelop >& kdevelop_log.txt This afternoon I encountered the memory leak once again. Managed to select Session > Quit from KDevelop, and though the window disappeared, the kdevelop process (PID 12200) kept running and consuming additional memory. Eventually I sent two SIGTERM signals to kill it. I have attached the heaptrack file and the first and last 1000 lines of the log file. Hopefully there is some helpful information here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #26 from Martin Fuhrer ---
Strange, heaptrack was running the kdevelop session for around eight hours (and
kdevelop was running smoothly for most of this time, using a stable amount of
memory when I checked a couple times during the first few hours). A few
additional details I forgot to mention yesterday:
* I unpacked the AppImage and ran kdevelop from the usr/bin/ directory within.
* The default Debian 7 gcc (v4.7.2) is too old to build heaptrack, so I used a
custom install of the gcc v4.8.5 compiler and runtime for the heaptrack session
(kdevelop exhibits the memory leak whether it uses the gcc v4.8.5 runtime or
the default v4.7.2 runtime).
* When the kdevelop process refused to quit (and continued eating up memory), I
sent SIGTERM to the kdevelop process (not the heaptrack process).
Here are all the commands I ran (from csh):
set DIR="/scratch/home/mfuhrer/sw/db7/src/kdevelop-5.2.1"
setenv LD_PRELOAD $DIR/exec_wrapper.so
setenv APPIMAGE_ORIGINAL_QML2_IMPORT_PATH ""
setenv APPIMAGE_ORIGINAL_LD_LIBRARY_PATH $LD_LIBRARY_PATH
setenv APPIMAGE_ORIGINAL_QT_PLUGIN_PATH $QT_PLUGIN_PATH
setenv APPIMAGE_ORIGINAL_XDG_DATA_DIRS $XDG_DATA_DIRS
setenv APPIMAGE_ORIGINAL_PATH $PATH
setenv APPIMAGE_ORIGINAL_PYTHONHOME ""
setenv QML2_IMPORT_PATH $DIR/usr/lib/qml
setenv LD_LIBRARY_PATH $DIR/usr/lib/:${LD_LIBRARY_PATH}
setenv QT_PLUGIN_PATH $DIR/usr/lib/qt5/plugins/
setenv XDG_DATA_DIRS $DIR/usr/share/:${XDG_DATA_DIRS}
setenv PATH $DIR/usr/bin:${PATH}
setenv KDE_FORK_SLAVES 1
setenv PYTHONHOME $DIR/usr/
setenv APPIMAGE_STARTUP_QML2_IMPORT_PATH $QML2_IMPORT_PATH
setenv APPIMAGE_STARTUP_LD_LIBRARY_PATH $LD_LIBRARY_PATH
setenv APPIMAGE_STARTUP_QT_PLUGIN_PATH $QT_PLUGIN_PATH
setenv APPIMAGE_STARTUP_XDG_DATA_DIRS $XDG_DATA_DIRS
setenv APPIMAGE_STARTUP_PATH $PATH
setenv APPIMAGE_STARTUP_PYTHONHOME $PYTHONHOME
setenv KDEV_DISABLE_PLUGINS KDevWelcomePage
setenv LD_LIBRARY_PATH
/vega/xp/ThirdParty/gcc/db7/xprel/lib64:${LD_LIBRARY_PATH}
cd $DIR/usr/bin
heaptrack kdevelop >& kdevelop_log.txt
The last line was executing for about eight hours (until I killed kdevelop).
Could the track file be truncated because I killed the kdevelop process? Is
there some way to monitor the track file during the heaptrack session?
Unfortunately I don't have KDE 5, so can't build the heaptrack GUI to verify
the track file.
--
You are receiving this mail because:
You are watching all bug changes.
[Heaptrack] [Bug 393387] support AppImage profiling
https://bugs.kde.org/show_bug.cgi?id=393387 Martin Fuhrer changed: What|Removed |Added CC||mfuh...@alumni.ucalgary.ca -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393420] New: Automatic spell checking: Word added to dictionary is still underlined after scrolling back into view
https://bugs.kde.org/show_bug.cgi?id=393420 Bug ID: 393420 Summary: Automatic spell checking: Word added to dictionary is still underlined after scrolling back into view Product: kdevelop Version: 5.2.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: mfuh...@alumni.ucalgary.ca Target Milestone: --- Open a C++ (*.cpp) or C (*.c) file (I couldn't replicate using a plain *.txt file) with two or more "pages" of code and enable Tools > Spelling > Automatic Spell Checking. Locate a word that is underlined red (i.e. flagged for incorrect spelling) among comments or strings in the source code. Right click on the word and select Spelling > Add to Dictionary. The word will no longer be underlined, but if the word scrolls out of view and then scrolls back into view, it will be underlined once again. If I restart KDevelop, the word is recognized as correct with no issues. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 Martin Fuhrer changed: What|Removed |Added Attachment #111039|0 |1 is obsolete|| Attachment #112098|0 |1 is obsolete|| Attachment #112099|0 |1 is obsolete|| --- Comment #30 from Martin Fuhrer --- Created attachment 112317 --> https://bugs.kde.org/attachment.cgi?id=112317&action=edit KDevelop log (PID 16665) KDevelop messages printed to the terminal. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 --- Comment #31 from Martin Fuhrer --- Created attachment 112318 --> https://bugs.kde.org/attachment.cgi?id=112318&action=edit KDevelop backtrace (PID 16665) Backtrace generated when I tried to quit KDevelop during memory leak. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 --- Comment #32 from Martin Fuhrer --- Hi Milian, thanks for the heaptrack fix. It appears to be working correctly now. I encountered the memory leak again this morning (workstation started freezing up), and tried to quit KDevelop. I waited several minutes until KDevelop crashed and attached the log and backtrace. The heaptrack file is very large so I've posted it for download from a third party site: https://mega.nz/#!sdMXxZBT!Pxv1UGEqS2ef73Q39IgtELcneWzwXHpgszxYeyBAmaw Reviewing the log it appears that there is some issue while libclang is parsing a source file. I am curious if this is what triggers the leak. I will try some more tests on my end... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392602] New: Contextual menu in Documents tool view is slow to appear
https://bugs.kde.org/show_bug.cgi?id=392602 Bug ID: 392602 Summary: Contextual menu in Documents tool view is slow to appear Product: kdevelop Version: 5.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: VCS: Perforce Assignee: kdevelop-bugs-n...@kde.org Reporter: mfuh...@alumni.ucalgary.ca Target Milestone: --- When right-clicking on a document (or a selection of documents) in the Documents tool view, a contextual menu normally pops up instantaneously. This is certainly the case when the Perforce plugin is disabled. If the Perforce plugin is enabled, when right-clicking on a single document, there is a brief delay (about 2 seconds) before the contextual menu appears. When selecting n documents and right-clicking on the selection, the delay increases by about n times (e.g. right clicking on five selected documents requires about 10 seconds before the contextual menu appears). This is problematic if, for example, I want to select multiple documents to close from the contextual menu. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 Martin Fuhrer changed: What|Removed |Added CC||mfuh...@alumni.ucalgary.ca -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402299] New: Refresh button in Find/Replace in Files view clears previous search
https://bugs.kde.org/show_bug.cgi?id=402299 Bug ID: 402299 Summary: Refresh button in Find/Replace in Files view clears previous search Product: kdevelop Version: 5.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mfuh...@alumni.ucalgary.ca Target Milestone: --- SUMMARY Clicking the Refresh button in the Find/Replace in Files tool view doesn't perform a refresh; rather, it clears the previous search. STEPS TO REPRODUCE 1. Open the Find/Replace in Files tool view. 2. Click the New Search button. 3. Enter a search pattern and click Search... 4. Any matched patterns will be displayed in the tool view panel. 5. Click the Refresh button. OBSERVED RESULT Matched patterns will be cleared from the view panel and the last search is removed from the drop-down menu (similar to clicking the Clear Search History button, except in this case only the last search is removed). EXPECTED RESULT The search on the pattern should be repeated. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402299] Refresh button in Find/Replace in Files view clears previous search
https://bugs.kde.org/show_bug.cgi?id=402299 --- Comment #1 from Martin Fuhrer --- Ran some additional tests and found that the Refresh button works as expected if no project is loaded. If I open a project (mine is Makefile-based), then performing a search as described and clicking Refresh clears the search. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402301] New: Unable to select matched patterns after performing a replace in Find/Replace in Files view
https://bugs.kde.org/show_bug.cgi?id=402301 Bug ID: 402301 Summary: Unable to select matched patterns after performing a replace in Find/Replace in Files view Product: kdevelop Version: 5.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mfuh...@alumni.ucalgary.ca Target Milestone: --- SUMMARY After performing a replace operation in the Find/Replace in Files view, the matches from the previous search are still displayed, but it is not possible to select a match to bring it up in the text editor (useful to verify that the replace operation succeeded). STEPS TO REPRODUCE 1. Click Find/Replace in Files. 2. Click the New Search button. 3. Enter a desired pattern and click Search... 4. Matched patterns will be displayed in the Find/Replace in Files view. You can select a line to bring up the matched pattern in the text editor. 5. Enter a string in the Replacement text field and click Replace. 6. Click on one of the matched patterns (now greyed out). OBSERVED RESULT Nothing happens. EXPECTED RESULT The matched pattern (which has now been replaced) for the selected line should be displayed in a text editor. This is the behaviour in KDevelop 4.x, and is useful to verify that the replacement operation succeeded. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402301] Unable to select matched patterns after performing a replace in Find/Replace in Files view
https://bugs.kde.org/show_bug.cgi?id=402301 Martin Fuhrer changed: What|Removed |Added Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402309] New: Code Browser fails to display documentation for Qt functions
https://bugs.kde.org/show_bug.cgi?id=402309
Bug ID: 402309
Summary: Code Browser fails to display documentation for Qt
functions
Product: kdevelop
Version: 5.3.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Documentation viewer
Assignee: kdevelop-bugs-n...@kde.org
Reporter: mfuh...@alumni.ucalgary.ca
Target Milestone: ---
SUMMARY
The Code Browser in Qt fails to display inline documentation for many Qt
functions. By the same token, when the Code Browser is not displayed, the pop
up box that appears when hovering the cursor over a function call in the text
editor also fails to display inline documentation for the same Qt functions. I
did not encounter these issues in KDevelop 4.x.
STEPS TO REPRODUCE
1. Place the following code into a document and open with KDevelop:
#include
void foo()
{
QString str;
str.append( "more " );
str.replace( "mo", "ca" );
str.trimmed();
}
2. Open the Code Browser (or observe the pop up box).
3. Hover the cursor over append. Documentation displays as expected.
4. Hover the cursor over replace. Documentation does not display as expected.
5. Hover the cursor over trimmed. Documentation does not display as expected.
OBSERVED RESULT
For (5), the Code Browser (or pop up box) displays:
QString trimmed()
Container: QString Access: public Kind: Function constant
Decl.: qstring.h :405 Show uses
Show documentation for QString::trimmed
EXPECTED RESULT
For (5), the code browser in KDevelop 4 displays full inline documentation:
QString trimmed()
Container: QString Access: public Kind: Function constant
Decl.: qstring.h :420 Show uses
Returns a string that has whitespace removed from the start and the end.
Whitespace means any character for which QChar::isSpace() returns true. This
includes the ASCII characters '\t', '\n', '\v', '\f', '\r', and ' '.
Example:
QString str = " lots\t of\nwhitespace\r\n ";
str = str.trimmed();
// str == "lots\t of\nwhitespace"
Unlike simplified(), trimmed() leaves internal whitespace alone.
See also simplified().
Show documentation for QString::trimmed
ADDITIONAL INFORMATION
Though clicking the "Show documentation for QString::trimmed" link allows the
documentation to be displayed in the Documentation viewer, this is much less
convenient than immediately seeing the inline documentation when hovering the
cursor over a function. It worked consistently in KDevelop 4.x, but frequently
fails to work in KDevelop 5.x. Perhaps a parsing issue?
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 402309] Code Browser fails to display documentation for Qt functions
https://bugs.kde.org/show_bug.cgi?id=402309 --- Comment #2 from Martin Fuhrer --- Ian, yes, I've encountered the one-element shift as well. So to summarize, I encounter one of three scenarios: * the inline documentation displays fine. * the inline documentation doesn't display (only the "Show documentation for Class::function" link is available). * the inline documentation displays but is for the next item. Also, in my description summary, I meant to write "The Code Browser in KDevelop..." -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368269] qch file cannot be added because QSQLITE driver not loaded (AppImage)
https://bugs.kde.org/show_bug.cgi?id=368269 Martin Fuhrer changed: What|Removed |Added CC||mfuh...@alumni.ucalgary.ca Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Martin Fuhrer --- I'm getting the exact same errors reported by Gregor in recent kdevelop AppImage distributions (currently 5.2.3). When I first start kdevelop, the following lines are printed to the console: QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: kdevelop.plugins.qthelp: Couldn't setup QtHelp Collection file and whenever I try to load a qch Qt documentation file I get: QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: QSqlDatabasePrivate::removeDatabase: connection 'GetNamespaceName-6723712-1' is still in use, all queries will cease to work. implying that no sql drivers are available. The following library does exist in the AppImage, but for some reason it doesn't appear to get recognized by QSqlDatabase: usr/lib/libsqlite3.so.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379551] Sudden huge memory leaks when using KDevelop for an extended amount of time
https://bugs.kde.org/show_bug.cgi?id=379551 Martin Fuhrer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #34 from Martin Fuhrer --- The clang issue in Milian's previous comment appears to have been resolved. I noticed that the KDevelop 5.3.0 AppImage is distributed with libclang.so.6 (KDevelop 5.2.x was using libclang.so.5). Good news is, I have been trying out KDevelop 5.3.0 for a week and haven't encountered the memory leak anymore. -- You are receiving this mail because: You are watching all bug changes.
