Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5933345
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T14:57:37+00:00 2026-05-22T14:57:37+00:00

Should I dispose CellEditor returned from EditingSupport.getCellEditor , and if so when should I

  • 0

Should I dispose CellEditor returned from EditingSupport.getCellEditor, and if so when should I do it.

On one of the tutorials on jface TableViewer I saw following snippet:

public class FirstNameEditingSupport extends EditingSupport {

    @Override
    protected CellEditor getCellEditor(Object element) {
        return new TextCellEditor(viewer.getTable());
    }

so would this method leak memory if cell was edited multiple times? Or should I just lazy initialize CellEditor:

 public class FirstNameEditingSupport extends EditingSupport {

    CellEditor editor;

    @Override
    protected CellEditor getCellEditor(Object element) {
        if(editor == null){
           editor = new TextCellEditor(viewer.getTable());
       }

       return editor;
    }
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T14:57:38+00:00Added an answer on May 22, 2026 at 2:57 pm

    The first snippet looks like a nasty leak to me if you use such a EditingSupport for ViewerColumns. Just have a look at the source of ColumnViewerEditor, the class handling lots of the work around CellEditors. There are lots of lines like

    if(part.getEditingSupport() != null)
    

    (with part being a ViewerColumn). These calls create a Text instance in the constructor of the TextCellEditor. But since the EditingSupport instance is not assigned, it will be GCed immediately. The Text instance will not be disposed (until its parent is disposed). Leak.

    So your second snippet seems way better.

    Which tutorial? Maybe you should report that.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

It seems to me that one should always properly dispose resources when calling Directory
One of the rules for implementing the Dispose method says: Throw an ObjectDisposedException from
Should I dispose GDI+ object before its creation? Is recommended to always Dispose GDI+
Many GDI+ classes implement IDisposable, but I'm not sure when I should call Dispose.
Should the folders in a solution match the namespace? In one of my teams
Certainly we should call Dispose() on IDisposable objects as soon as we don't need
My class is inherited from UnityContainer (from Unity 2.0), here is source code: public
Should I call .Dispose() after returning an object that implements IDisposable? myDisposableObject Gimme() {
We are getting the following warning from Code Analysis in Visual Studio 2010 and
I have this piece of code for reading from an excel cell: public T

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.