Java Out Of memory Errors when viewing migrated bundles

When viewing or assigning migrated bundles there is an out of memory error:

[ERROR] [07/29/2010 09:37:36.639] [1668] [ZenworksWindowsService] [33] []
[Bundle] [Bundle.ItemCreationError] [Error creating item to represent bundle:
8ec39cbc54bd482184a9f1bb778f990c Exception: Exception of type
'System.OutOfMemoryException' was thrown.  Stack:    at
System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32
length, Int32 capacity)
   at System.Text.StringBuilder.GetNewString(String currentString, Int32
requiredLength)
   at System.Text.StringBuilder.Append(String value)
   at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator
evaluator, Regex regex, String input, Int32 count, Int32 startat)
   at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator
evaluator, Int32 count, Int32 startat)
   at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator
evaluator)
   at System.Text.RegularExpressions.Regex.Replace(String input, String
pattern, MatchEvaluator evaluator)
   at Novell.Zenworks.Zmd.ConfigManager.ParseMacros(Session session, String&
inputString, ConfigMacro() extraMacros)
   at Novell.Zenworks.AppModule.AppItem.UpdateAppData(Session session, AppData
appData)
   at Novell.Zenworks.AppModule.AppActionItem.UpdateAppData(Session session,
AppData appData)
   at Novell.Zenworks.AppModule.AppItem.initAppItem(Session session, AppData
data, String zone)
   at Novell.Zenworks.AppModule.AppActionItem.initBaseItem(Session uiSession,
AppData data, Session serviceSession, IService service)
   at Novell.Zenworks.AppModule.AppItemManager.CreateNewActionItem(Session
session, AppData app, Session serviceSession, IService service, Boolean
createdFromUserProcess, Boolean createAsADependentApp)] [] []

This is fixed in version 11.1 - see KB 7008746 "ZENworks Configuration Management 11.1 - update information and list of fixes" which can be found at https://www.novell.com/support

Workaround:
In this situation deleting the bundle and then re-migrating it using the migrate as an MSI option resolved the problem.

The bundle in question was migrated from an application object that had thousands of ini and registry operations and hundreds of fill files.