No, not really yet. It happened when I was opening the editor. So I
would guess that's some sort of bad dltk integration, either a bug in
the old dltk version or a wrong usage of the dltk framework.
If I have some spare time next week, I'll try to find the leak with a
profiler or something.
Peter
Am 12.08.2011 15:38, schrieb Marshall Schor:
any idea what's filling up perm space?
-Marshall
On 8/12/2011 8:01 AM, Peter Klügl (JIRA) wrote:
[
https://issues.apache.org/jira/browse/UIMA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084057#comment-13084057
]
Peter Klügl commented on UIMA-2206:
-----------------------------------
Tested the new projects for basic functionality. First, I had some problems
with the MaxPermSize, but all worked fine with -XX:MaxPermSize=128m added to
the Eclipse arguments. If further problems or bugs occur, then they should be
fixed in new issues.
I'm closing this issue.
Further restructuring and renaming of the TextMarker projects
-------------------------------------------------------------
Key: UIMA-2206
URL: https://issues.apache.org/jira/browse/UIMA-2206
Project: UIMA
Issue Type: Task
Components: TextMarker
Reporter: Peter Klügl
Assignee: Peter Klügl
Attachments: TextMarker.zip
The TextMarker projects should be further restructured, especially the dltk
plugins should be merged. That will ease the migration to the maven build
process. The engine project should then be separated to a normal java project
and a fetcher plugin. This will be done not until the migration to maven.
This restructuring enforces some renaming. Therefore, also additional renaming
is performed in this task. All projects will be adapted to the UIMA convention
for eclipse plugins. The namespaces will be unified to
org.apache.uima.textmarker.* and the mention of dltk will be replaced by ide.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
