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 184782 - why does debugging start mercurial refresh?
Summary: why does debugging start mercurial refresh?
Status: VERIFIED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Solaris
: P2 normal (vote)
Assignee: issues@debugger
URL:
Keywords:
: 184783 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-22 22:55 UTC by ivan
Modified: 2010-05-11 14:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 ivan 2010-04-22 22:55:39 UTC 

    


    


      



        
          Comment 1
        

        
          ivan

        

        
        

        
          2010-04-22 23:01:30 UTC
        

      






I'm using a self-built "basic" NB circa 100421 ... when I start 
debugging the disk goes wild and really slows things down.
One of the reasons is that a mercurial refresh task gets started.

This doesn't make much sense.

    


    


      



        
          Comment 2
        

        
          Daniel Prusa

        

        
        

        
          2010-04-23 11:34:14 UTC
        

      






What do you mean by mercurial refresh? Is it scanning and indexing of chekouted sources (done by java module), or is it update of the sources from repository.

There is issue 183405 which is related to the first case. Have you encountered the same situation?

    


    


      



        
          Comment 3
        

        
          Daniel Prusa

        

        
        

        
          2010-04-23 11:41:04 UTC
        

      






According to the second report, issue 184783, it really seems that it is about scanning of sources.

    


    


      



        
          Comment 4
        

        
          Daniel Prusa

        

        
        

        
          2010-04-23 11:43:45 UTC
        

      






*** Bug 184783 has been marked as a duplicate of this bug. ***

    


    


      



        
          Comment 5
        

        
          Daniel Prusa

        

        
        

        
          2010-04-29 13:00:37 UTC
        

      






Is this still reproducible after issue 183405 has been fixed?

    


    


      



        
          Comment 6
        

        
          ivan

        

        
        

        
          2010-05-05 07:10:39 UTC
        

      






(In reply to comment #5)
> Is this still reproducible after issue 183405 has been fixed?

Sorry, I haven't had the chance to upgrade my "use" NB. I'll let you
know as soon as I upgrade and play with it a bit.

    


    


      



        
          Comment 7
        

        
          Martin Entlicher

        

        
        

        
          2010-05-06 13:25:08 UTC
        

      






Resolving as incomplete for now. I did not reproduce that debugger would trigger Mercurial refresh. Debugger does not call any filesystem refresh directly, therefore this can not be visible in any thread dump. If this really happens to you on a regular basis (IMHO it was just a coincidence), please provide steps to reproduce.

    


    


      



        
          Comment 8
        

        
          Marian Mirilovic

        

        
        

        
          2010-05-11 14:22:56 UTC
        

      






I played with this a little bit, but has not been able to reproduce it yet - verified/incomplete