what i observe right now is when i click on any step in authoring tree
other than the drawing tool. everything is fine. but when i click on
the drawing tool, it takes forever and then starts with the error. i
tried to increase my heap in my eclipse. that did not work. so what i
am doing now is trying to get a profiler up and running and see the
whats going on.
The regular otrunk drawing tool demo runs fine.
-Tony
On [Jun 10], at 2:18 PM, Sam Fentress wrote:
> Anthony Perritano <[EMAIL PROTECTED]> writes:
> Sam,
> Thanks. i think that did it as far as switching to the new code
> base. however when i create a new instance of the drawing tool i get
> the following. The drawing tool comes up with no toolbar, just a
> save button. and then this happens when i resize the window:
>
> Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError:
> Java heap space
> at java.util.Vector.<init>(Vector.java:113)
> ...
> at
> org
> .concord
> .otrunk
> .graph
> .OTDataDrawingToolEditView
> .createEditPanel(OTDataDrawingToolEditView.java:112)
>
>
>
> That's very strange. The edit view shouldn't be doing anything
> complicated at all. The line that it's stalling at is just
>
> bgImageText.setText("http://";);
>
> which should not at all memory intensive.
>
> Could a memory intensive procedure be going on in an unrelated
> thread, which is using up the available memory, and this command
> just happens to be the one that pushes it over?
>
> Does the exception always occur at the same place? Does the drawing
> authoring example work from Eclipse?
>
> Sam
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---
