This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 244334 - 100% CPU usage after composer update
Summary: 100% CPU usage after composer update
Status: RESOLVED DUPLICATE of bug 244197
Alias: None
Product: php
Classification: Unclassified
Component: Twig (show other bugs)
Version: 8.0
Hardware: PC Linux
: P1 normal (vote)
Assignee: Ondrej Brejla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-06 16:23 UTC by bugmenot1
Modified: 2014-05-06 17:40 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
cpu usage at 100% after composer update (184.66 KB, application/octet-stream)
2014-05-06 17:25 UTC, bugmenot1 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bugmenot1 2014-05-06 16:23:00 UTC 
After update the component from version 0.19.1 to 0.19.2, the project background syncronization is blocked when composer vendor are installed.
So the CPU usage of one core is blocked at 100%.
Comment 1 Tomas Mysik 2014-05-06 16:27:15 UTC 
Please, reproduce your problem and create a profiler snapshot [1] (about 30 seconds should be OK). Reopen this issue and attach the snapshot here.

Thanks.
[1] http://wiki.netbeans.org/FaqProfileMeNow
Comment 2 bugmenot1 2014-05-06 17:25:10 UTC 
Created attachment 147144 [details]
cpu usage at 100% after composer update
Comment 3 bugmenot1 2014-05-06 17:27:36 UTC 
Attachement added.

Apparently it's not related to the composer component update.
I just started an empty PHP project with only "symfony/symfony" as a composer dependency.
After composer install, the background project scan never ends and block CPU usage at 100%.
Comment 4 Tomas Mysik 2014-05-06 17:31:30 UTC 
Problem in Twig:

org.netbeans.modules.php.twig.editor.parsing.TwigParser.parse()	99.35093	44 648 ms (99,4%)	44 648 ms	1

@reporter: If you disable Twig module (in Tools > Plugins), it should work.

Reassigning, please evaluate. Thanks.
Comment 5 Ondrej Brejla 2014-05-06 17:40:44 UTC 

*** This bug has been marked as a duplicate of bug 244197 ***