Bug 232835 - Kdevelop background parsing hangs on javascript
Summary: Kdevelop background parsing hangs on javascript
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-03-31 13:55 UTC by Matthijs
Modified: 2018-10-21 04:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthijs 2010-03-31 13:55:08 UTC
Version:           3.9.99 (using KDevPlatform 0.9.99) (using 4.4.1 (KDE 4.4.1), Arch Linux)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.33-ARCH

I have a project using javascript and PHP. Whenever I open that project, the background parser starts but its progress stays at 0%. I am able to use the editor, but all autocompletion features don't work obviously.

If I close KDevelop, the process continues running, presumably because it is still busy.

None of this happens when opening a C++ project.
Comment 1 Milian Wolff 2010-03-31 14:05:59 UTC
please provide the javascript file that results in the hang, you can enable PHP & KDevelop language debug areas in kdebugdialog and see which file it tries to parse when.
Comment 2 Matthijs 2010-03-31 14:27:18 UTC
When started from the command line, KDevelop gave some output, but nothing about parsing a file. I killed it with Ctrl-C to try again. After I did that, I cannot reproduce this anymore.

Now KDevelop parses the project fine. Some of the debug messages by KDevelop were about removing stale lockfiles, but nothing I can remember not being there currently.
Comment 3 Andrew Crouthamel 2018-09-20 22:07:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:21:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!