Bug 245908 - [misc] same project properties duplicated in memory
Summary: [misc] same project properties duplicated in memory
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-01 20:35 EDT by Jeff McAffer CLA
Modified: 2023-03-05 06:47 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2008-09-01 20:35:51 EDT
I happened to be using the Core Tools poking around (don't ask) and noticed that there are many duplicate project preferences related to JDT.  Essentially all of the projects in my workspace have project specific prefs for JDT core and UI things.  The problem is that all projects have exactly the same settings in typical configurations (or at least there is a small set of differences).  Overall the 19,000 prefs take up nearly 5MB of heap. A quick calculation estimate says that about 15000 of those prefs are related to JDT (about 400 prefs per project and 50 projects in my workspace).  Not sure if hte space allocation matches but certainly there must be some overhead in even having the keys in the structure etc.  I'm assuming that the keys are interned somehow.
Comment 1 Dani Megert CLA 2008-09-02 02:29:22 EDT
Yes, they are duplicated per project and you find most of them from JDT because most other plug-ins don't offer you to set the preferences per project and store them in the repository. Unfortunately we do not have a story to share global settings in the repository or let a project refer to some other (settings) project from which it could inherit the settings.

I'm inclined to mark this as duplicate of bug 194414.
Comment 2 Eclipse Genie CLA 2019-02-15 01:14:43 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2021-02-05 02:58:08 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2023-03-05 06:47:13 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.