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.
| Summary: | Turn off memory toolbar for M9 | ||
|---|---|---|---|
| Product: | platform | Reporter: | jrojcek <jrojcek> |
| Component: | Window System | Assignee: | Antonin Nebuzelsky <anebuzelsky> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | CC: | issues |
| Priority: | P1 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 99509, 100933 | ||
|
Description
jrojcek
2007-04-19 13:13:47 UTC
Rising priority to P1 so that we don't forget about it. No problem to turn the memory toolbar off for M9 as soon as the milestone branch is created on Thursday. But do we really want to do that? We usually turn memory toolbar off for FCS. With preview we want to get as much feedback from users as possible. And feedback about memory consumption and any related problems is very valuable for us at this point. I would say so that it should be removed for M9. Regarding feedback. How users use the memory toolbar to provide feedback about performance? Is it like "suddenly I saw the memory is at 200MB and it didn't go down". Or is it something else? How many reports do we get from users who directly observer something's wrong when they see the memory toolbar? I'm trying to understand how really helpful is the memory toolbar for gathering performance feedback. After M9... My opinion is that the memory meter should be visible in the status line becase it's more about the status information than about an action shortcut. Keep in mind it is clickable - it invokes garbage collector. Turned off on release60-m9 branch. v/c |