Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329711 - [Progress] AccessibleListener leaked in ProgressAnimationItem
Summary: [Progress] AccessibleListener leaked in ProgressAnimationItem
Status: CLOSED DUPLICATE of bug 315620
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.7   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Prakash Rangaraj CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-08 16:31 EST by Nick Edgar CLA
Modified: 2010-11-12 01:14 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2010-11-08 16:31:33 EST
In ProgressAnimationItem.initButton, it does:

    	toolbar.getAccessible().addAccessibleListener(new AccessibleAdapter() {
        	public void getName(AccessibleEvent e) {
        		e.result = tt;
        	}
        });

initButton can be called many times over the life of the item, though, so a new listener gets added each time.

One possible fix is to add the listener when the toolbar is created, and use toolbar.get/setData() to carry the name.
Comment 1 Prakash Rangaraj CLA 2010-11-09 00:44:54 EST
Sounds like dup of Bug#315620, but the patch doesn't contain the fix for this one.
Comment 2 Dani Megert CLA 2010-11-09 02:58:16 EST
(In reply to comment #1)
> Sounds like dup of Bug#315620,
Agreed.

> but the patch doesn't contain the fix for this one.
The patch fixed things at a higher level.

Nick, can you please try 3.6.1 or newer?
Comment 3 Prakash Rangaraj CLA 2010-11-12 01:14:11 EST
(In reply to comment #2)
> (In reply to comment #1)
> > Sounds like dup of Bug#315620,
> Agreed.
> 
> > but the patch doesn't contain the fix for this one.
> The patch fixed things at a higher level.
> 
> Nick, can you please try 3.6.1 or newer?

Nick, 

    I'm closing this bug. Please try it on 3.6.1 and if its reproducible, reopen the original bug (Bug# 315620) and add your comments.

*** This bug has been marked as a duplicate of bug 315620 ***