Re: More WOLips questions: HTML formatting, memory leaks?

Edgar Klein <[email protected]> Tue, 24 Jun 2008 11:54:12 -0600
Newsgroups gmane.comp.web.webobjects.devel
Message-ID <[email protected]>
On 19-Jun-08, at 8:22 AM, Will Scheidegger wrote:

> Once again, the help was _fast_ and _really helpful_!
>
> On 19.06.2008, at 15:34, Mike Schrag wrote:
>
>>> When I format a components HTML file (following this: http://wiki.objectstyle.org/confluence/display/WOL/Refactor+-+Format+HTML+Feature) 
>>>  my HTML-Code is pretty crippled afterwards with
>>> 	- spaces before and after the "=" symbol in attributes (i.e.  
>>> <webobject name = "TextField9" /> instead of <webobject  
>>> name="TextField9" />)
>>> 	- empty tags being shortened (i.e. <td /> instead of <td></td>)
>>> 	- and some funny effects where I'm not 100% sure that it was  
>>> Eclipse messing things up (e.g. <br ></br>)
>> You didn't include what version of WOLips you're running but you're  
>> definitely not on the latest stable.  I don't know what you mean  
>> about your HTML being "crippled."  None of these actually sound  
>> like a problem (just style preferences).  The only one that's a  
>> little weird (but not wrong) is <br></br>, which I just tested, and  
>> it become <br/> in the new build.  The spaces around the equals is  
>> a preference -- Prefs=>WOLips=>HTML Editor=>XML
>
> Yes, you're right, the code is not crippled - it's just needs  
> getting used to because I've never seen a tool which formats its  
> code like this. But the preference settings you've pointed me to of  
> course did solve the problem. Thanks!
>
>
>>> Then I strongly thing that my setup has a serious memory leak.  
>>> When I run a wo app out of Eclipse which works fine in production  
>>> with only 32MB RAM, I always get out of memory exceptions after a  
>>> very short time (e.g. 20 requests) even when I double the amount  
>>> of ram for the app. Does anyone else experience similar behavior?
>> Eclipse isn't really involved in the memory management of your  
>> application -- it runs in a completely separate VM.  If you're  
>> running in debug mode (which you should be), that will definitely  
>> take up more ram.  When you say you are doubling the amount of ram  
>> for the app, where and how are you exactly specifying that?
>
> "Debug mode" = Launching the app with the "Debug" button in Eclipse?  
> No, so far I always lunched it with the "Run" button. I set the RAM  
> in the "Run" dialog under the WOApplication's VM arguments.

WOWODC: "Always run your apps in debug mode".

You could also change the eclipse.ini file (.../eclipse/Eclipse.app/ 
Contents/MacOS/eclipse.ini) and set the parameter -Xmx to let say  
512m. This saves me when I clean my workspace so that Eclipse doesn't  
run out of memory.

Edgar