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 68438 - Investagate impact of disabling memory meter on the IDE
Summary: Investagate impact of disabling memory meter on the IDE
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: David Simonek
URL:
Keywords: UI, UMBRELLA
Depends on:
Blocks: 62914 67847 67898 67980 70985
  Show dependency tree
 
Reported: 2005-11-10 09:48 UTC by Marian Mirilovic
Modified: 2010-04-22 09:14 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2005-11-10 09:48:05 UTC
It looks like disabling memory meter has an umpredictable impact on the
enabled/disabled actions, progress bar, opened windows and other UI issues.

All these issues are hard to find, because the memory meter is enabled by
default during the whole development cycle and become disabled only for Betas,
RCs and Final release. 

We would like to know why it has such impact on the whole IDE?

Here is the list of already reported issues, reproducible only with disabled
Memory Meter :
issue 67847 Menu item Show CVS Status Labels not active
issue 67898 Navigator doesn't display content of XML file
issue 67980 Submenus under CVS | Branches not active
issue 68345 No progress bar when memory meter disabled
issue 62914 Form Ed. specific windows not dismissed when in Source view
Comment 1 _ alexlamsl 2005-12-08 17:23:42 UTC
all related issues fixed.
Comment 2 Marian Mirilovic 2005-12-09 09:19:44 UTC
I hope there isn't another hidden impact ;) ... verified
Comment 3 Milan Kubec 2005-12-12 09:03:37 UTC
I thought that this task would be fixed after we find out what is the actual
problem there.
Comment 4 Milan Kubec 2006-01-04 11:41:39 UTC
Reopening, I've found another issue #70985. 
This issue should be closed after we find out the real cause of those problems.
Comment 5 Stanislav Aubrecht 2007-08-03 18:03:40 UTC
the core problem was that the memory meter was/had been revalidating itself with each change in available memory. that
caused invalidated/repaint of the whole window.

...closing as fixed
Comment 6 Marian Mirilovic 2010-04-22 09:14:25 UTC
v/c