• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
WoResourceManager.stringForKey, slow app and out of memory errors
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WoResourceManager.stringForKey, slow app and out of memory errors


  • Subject: WoResourceManager.stringForKey, slow app and out of memory errors
  • From: Fabrice Pipart <email@hidden>
  • Date: Thu, 22 Nov 2007 10:18:01 +0100

Hi dear list !

Like many I guess, I am adapting my project to Leopard and WO 5.4

I have many details to solve but one is more a problem than others.
My app is terribly slowed down under Leopard.
But now it becomes even more obvious why.

I very often get that kind of error after something like 20 clicks in my app :

Caused by: java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding$ConverterSD.decode(StringCoding.java:142)
at java.lang.StringCoding.decode(StringCoding.java:228)
at java.lang.String.<init>(String.java:405)
at com.webobjects.foundation._NSStringUtilities.stringForBytes(_NSStringUtilities.java:110)
at com.webobjects.foundation._NSStringUtilities.stringForBytes(_NSStringUtilities.java:147)
at com.webobjects.foundation.NSPropertyListSerialization.propertyListFromData(NSPropertyListSerialization.java:1749)
at com.webobjects.appserver.WOResourceManager._stringsTable(WOResourceManager.java:539)
at com.webobjects.appserver.WOResourceManager._cachedStringsTable(WOResourceManager.java:567)
at com.webobjects.appserver.WOResourceManager._cachedStringForKey(WOResourceManager.java:581)
at com.webobjects.appserver.WOResourceManager._stringForKey(WOResourceManager.java:595)
at com.webobjects.appserver.WOResourceManager.stringForKey(WOResourceManager.java:624)
at com.easyshadow.global.utilities.ApplicationUtilities.translate(ApplicationUtilities.java:91)

My translate method does the following :
        WOResourceManager rm = Application.application().resourceManager();
        return rm.stringForKey(keyToTranslate,"MyStringsFileName",null,null,languages);
My localized .strings files are UTF-16.

I replaced the translate method with a wonder equivalent (or almost since it does not initialize properly, but that was just to prove woresourcemanager is faulty) :
ERXLocalizer.currentLocalizer().localizedStringForKeyWithDefault(keyToTranslate);

My app becomes responsive again and does not crash any more.


Does anyone have an idea why this happens?


Fabrice Pipart
www.easyshadow.com
EasyMediaOnline
Digital Signage Software

Easyshadow
Palais de la Scala
1 avenue Henri Dunant
Suite 1155
MC - 98000 Monaco

Skype: fabrice.pipart
Tel.  +377 97 98 21 04 (direct)
Fax. +377 97 70 88 07


Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: WoResourceManager.stringForKey, slow app and out of memory errors
      • From: Daryl Lee <email@hidden>
  • Prev by Date: Re: Nested NSArray of Strings - Generics - WO5.4
  • Next by Date: Re: Foreign Key Constraints and EOModeler
  • Previous by thread: Re: Nested NSArray of Strings - Generics - WO5.4
  • Next by thread: Re: WoResourceManager.stringForKey, slow app and out of memory errors
  • Index(es):
    • Date
    • Thread