Re: Find usages appears to be broken in NetBeans 24

[Simon IJskes - QCG <si...@qcg.nl>]

I know reporting these problems are really getting on everybodies 
nerves. I apologize in advance. But please don't reject them on the 
basis of not having a good reproducer.

I've noticed in the past, behaviour of background processes, that looks 
there is some kind of deadlock, hanging lock condition, or something 
related to concurrency. so it feels. (i know, very vague).

I develop with a big code base, so some background processes take 
noticably longer.

The problems are mostly in things i suspect are background processes, 
like error indicators in the right bar of the editor window. error 
indicators on files that are not in sync. alt-space method suggestion 
popups that do not work.

Generally they are the most noticable (if at all, not sure here), when 
i've started a daemon and it is still running. when i develop a client- 
server setup, i keep both maven projects open in the IDE, en if i 
develop on the client, i keep the server runing. and vice versa. The 
problem in reproducing here, it doesn't happen all the time. I mix my 
development sessions with running, and then debugging, etc. And then 
suddenly all the (background?) stuff that is very helpfull, like 
mentioned before stop working. To recover i need to stop all processes 
running under command of the IDE. Mostly that does it. Sometimes not, 
then i have to leave the IDE.

Now for the difficult question, how to reproduce, and how to collect 
information that points us nearer to the problem.

I have several versions on my desktop, the last one that exhibited this 
behaviour was 24. i've just installed 25-rc1 to see if there are 
improvements.

Let me conclude: i'm very gratefull for the time people put in netbeans, 
and other apache projects. When i have i sense of ownership for a 
project, i feel personally responsible for any errors/bugs that get 
reported, even if i should not be. I hope i'm not causing any extra 
stress by reporting this.

Gr. Simon


On 12/22/24 19:21, Ulrich Mayring wrote:
> Am Freitag, Dezember 20, 2024 18:21 CET, schrieb Michael Bien 
> <mb...@gmail.com>:
> 
>> For other issues please try to find a reproducer and open a proper bug
>> report (or add more details to existing reports).
>>
>> Posts like this are close to impossible to investigate if they don't
>> even mention the project type or any other details.
>>
>> best regards,
>> michael
>>
> Agreed. My point was to give a few examples of unreproducible problems 
> in Netbeans (Gradle/Java projects all of them) and saying that the 
> current problem talked about here also happens to me unreproducibly. So 
> it's probably some kind of architectural issue that can affect Netbeans 
> in many different ways, maybe something to do with an index becoming 
> inconsistent or some other race condition. The only (and I would say 
> slim) chance of deterministically fixing this is if the various reports 
> ring a bell with someone, who is deeply familiar with Netbean's internal 
> design.
> 
> I haven't been successful in finding a reproducer for any of those 
> issues, but managed to live with them by restarting / reloading. The 
> good news is that at some point these issues will simply disappear (as 
> indeed some others have in the past), because someone changes some 
> internal behavior in NB for a completely different reason.
> 
> Kind regards,
> 
> Ulrich
> 


-- 
create firmware without programming https://www.bendyroad.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
For additional commands, e-mail: users-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists