apache / apache/netbeans

Background Scanning of the Project

Open
#4,967 4 comments 1 reaction 0 assignees View on GitHub
JavaScript kind:bug needs:triage PHP
Dominant language
Java
Stars
3.1k
Forks
935
Avg merge
2d 3h
Merged PRs (30d)
17

Description

### Apache NetBeans version

Apache NetBeans 15

### What happened

On startup, after the project opens it scans all the code to map all the code to enable jumps to called functions and function lookup.

We have large project and have just migrated to PHP 8.1 hence the move to NB 15. When the project opens it takes a very long time to scan the code and eventually errors with a GC overflow. This leaves me with no intellisense or click through to called functions and is slowing my work rate. I have tried clearing the cache and this made no difference.

I suspect it is failing in the javascript parts of the project. The public folder contains all the distributable javascript. Is there any way the background scanning process can be configured to omit the Public Folder.

### How to reproduce

_No response_

### Did this work correctly in an earlier version?

Apache NetBeans 12.6 or earlier

### Operating System

Windows 11

### JDK

Don't know

### Apache NetBeans packaging

Apache NetBeans provided installer

### Anything else

This occurs every time I open Netbeans, sometimes it hangs with a white flashing window. My PC has an Intel I7 processor and 16GB of ram.

### Are you willing to submit a pull request?

No

### Code of Conduct

Yes

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the startup scan on a large PHP project containing a distributable JavaScript public folder, using the reported Apache NetBeans 15 setup if available. Trace the background scanning entry point and any configuration affecting excluded folders; done means the project opens without GC overflow or hangs while preserving code navigation and lookup.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.