Re: [WiX-users] memory usage
Ok, We'll do it on Monday, And I'll come back to you with the result then. :) Until... have a nice Weekend. :) Regards, Tamas Rob Mensching wrote: Any profiler, the one in VS2005 would probably work. You can also do a kind of poor man's profiling by using a debugger and PerfMon to watch the allocated memory. *From:* TibTam [mailto:[EMAIL PROTECTED] *Sent:* Friday, December 08, 2006 12:21 *To:* Rob Mensching *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] memory usage What kind of profiler do you mean? I'm surprised too, one of my collegues wants me to solve this issue. :) Rob Mensching wrote: I'm not aware of any changes. You could stick a profiler on it and see where the memory is blowing up. I'm a little surprised though because there are teams that have MSI files double this size doing just fine inside Microsoft. -Original Message- From: TibTam [mailto:[EMAIL PROTECTED] Sent: Friday, December 08, 2006 11:45 To: Rob Mensching Cc: wix-users@lists.sourceforge.net <mailto:wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] memory usage Well.. We build a package. Made some development, but nothing changed in the Wix source files. After this Wix used at least double of the memory it usually uses, and we got this error. A file change or something like this can cause wix to eat the memory? Did anybody see this kind of error? Tamas Rob Mensching wrote: Usually that error occurs because you ran out of memory. I'm not aware of any other cases. -Original Message- From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi Sent: Thursday, December 07, 2006 23:05 To: wix-users@lists.sourceforge.net <mailto:wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] memory usage Thanks, i'll take a look. What can be the cause of this error (still the same, big, problematic package)?: candle.exe : error CNDL0001 : Exception of type 'System.OutOfMemoryException' was thrown. Exception Type: System.OutOfMemoryException Stack Trace: 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.IO.StringWriter.Write(String value) at System.Xml.XmlTextEncoder.Write(String text) at System.Xml.XmlTextWriter.WriteString(String text) at System.Xml.XmlWriter.WriteAttributeString(String localName, String value) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessReader(Boolean include, XmlReader reader, XmlWriter writer, Int32 offset) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessInclude(String includePath, XmlWriter writer) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessReader(Boolean include, XmlReader reader, XmlWriter writer, Int32 offset) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.Process(String sourcePath) at Microsoft.Tools.WindowsInstallerXml.Tools.Candle.Run(String[] args) light.exe : error LGHT0001 : Exception of type 'System.OutOfMemoryException' was thrown. Exception Type: System.OutOfMemoryException Stack Trace: at System.String.CtorCharArrayStartLength(Char[] value, Int32 startIndex, Int32 length) at System.Xml.XmlTextReaderImpl.NodeData.get_StringValue() at System.Xml.XmlTextReaderImpl.get_Value() at System.Xml.XmlTextReader.get_Value() at System.Xml.XmlValidatingReaderImpl.get_Value() at System.Xml.Schema.BaseValidator.ValidateText() at System.Xml.Schema.XsdValidator.Validate() at System.Xml.XmlValidatingReaderImpl.ProcessCoreReaderEvent() at System.Xml.XmlValidatingReaderImpl.Read() at System.Xml.XmlValidatingReader.Read() at Microsoft.Tools.WindowsInstallerXml.Field.Parse(XmlReader reader) at Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseTuple(Intermediate intermediate, X
Re: [WiX-users] memory usage
What kind of profiler do you mean? I'm surprised too, one of my collegues wants me to solve this issue. :) Rob Mensching wrote: I'm not aware of any changes. You could stick a profiler on it and see where the memory is blowing up. I'm a little surprised though because there are teams that have MSI files double this size doing just fine inside Microsoft. -Original Message----- From: TibTam [mailto:[EMAIL PROTECTED] Sent: Friday, December 08, 2006 11:45 To: Rob Mensching Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] memory usage Well.. We build a package. Made some development, but nothing changed in the Wix source files. After this Wix used at least double of the memory it usually uses, and we got this error. A file change or something like this can cause wix to eat the memory? Did anybody see this kind of error? Tamas Rob Mensching wrote: Usually that error occurs because you ran out of memory. I'm not aware of any other cases. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi Sent: Thursday, December 07, 2006 23:05 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] memory usage Thanks, i'll take a look. What can be the cause of this error (still the same, big, problematic package)?: candle.exe : error CNDL0001 : Exception of type 'System.OutOfMemoryException' was thrown. Exception Type: System.OutOfMemoryException Stack Trace: 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.IO.StringWriter.Write(String value) at System.Xml.XmlTextEncoder.Write(String text) at System.Xml.XmlTextWriter.WriteString(String text) at System.Xml.XmlWriter.WriteAttributeString(String localName, String value) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessReader(Boolean include, XmlReader reader, XmlWriter writer, Int32 offset) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessInclude(String includePath, XmlWriter writer) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessReader(Boolean include, XmlReader reader, XmlWriter writer, Int32 offset) at Microsoft.Tools.WindowsInstallerXml.Preprocessor.Process(String sourcePath) at Microsoft.Tools.WindowsInstallerXml.Tools.Candle.Run(String[] args) light.exe : error LGHT0001 : Exception of type 'System.OutOfMemoryException' was thrown. Exception Type: System.OutOfMemoryException Stack Trace: at System.String.CtorCharArrayStartLength(Char[] value, Int32 startIndex, Int32 length) at System.Xml.XmlTextReaderImpl.NodeData.get_StringValue() at System.Xml.XmlTextReaderImpl.get_Value() at System.Xml.XmlTextReader.get_Value() at System.Xml.XmlValidatingReaderImpl.get_Value() at System.Xml.Schema.BaseValidator.ValidateText() at System.Xml.Schema.XsdValidator.Validate() at System.Xml.XmlValidatingReaderImpl.ProcessCoreReaderEvent() at System.Xml.XmlValidatingReaderImpl.Read() at System.Xml.XmlValidatingReader.Read() at Microsoft.Tools.WindowsInstallerXml.Field.Parse(XmlReader reader) at Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseTuple(Intermediate intermediate, XmlReader reader, Section section, TableDefinition tableDef) at Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseTable(Intermediate intermediate, XmlReader reader, Section section, TableDefinitionCollection tableDefinitions) at Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseSection(Intermediate intermediate, XmlReader reader, TableDefinitionCollection tableDefinitions) at Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseIntermediate(Intermediate intermediate, XmlReader reader, TableDefinitionCollection tableDefinitions, Boolean suppressVersionCheck) at Microsoft.Tools.WindowsInstallerXml.Intermediate.Load(XmlReader reader, String path, TableDefinitionCollection tableDefinitions, Boolean suppressVersionCheck) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) -- View this message in context: http://www.nabble.com/memory-usage-tf2774539.html#a7753597 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---
Re: [WiX-users] memory usage
Well.. We build a package. Made some development, but nothing changed in the Wix source files. After this Wix used at least double of the memory it usually uses, and we got this error. A file change or something like this can cause wix to eat the memory? Did anybody see this kind of error? Tamas Rob Mensching wrote: > Usually that error occurs because you ran out of memory. I'm not aware of > any other cases. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi > Sent: Thursday, December 07, 2006 23:05 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] memory usage > > > Thanks, i'll take a look. > > What can be the cause of this error (still the same, big, problematic > package)?: > > candle.exe : error CNDL0001 : Exception of type > 'System.OutOfMemoryException' was thrown. > > Exception Type: System.OutOfMemoryException > > Stack Trace: >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.IO.StringWriter.Write(String value) >at System.Xml.XmlTextEncoder.Write(String text) >at System.Xml.XmlTextWriter.WriteString(String text) >at System.Xml.XmlWriter.WriteAttributeString(String localName, String > value) >at > Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessReader(Boolean > include, XmlReader reader, XmlWriter writer, Int32 offset) >at > Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessInclude(String > includePath, XmlWriter writer) >at > Microsoft.Tools.WindowsInstallerXml.Preprocessor.PreprocessReader(Boolean > include, XmlReader reader, XmlWriter writer, Int32 offset) >at Microsoft.Tools.WindowsInstallerXml.Preprocessor.Process(String > sourcePath) >at Microsoft.Tools.WindowsInstallerXml.Tools.Candle.Run(String[] args) > > > light.exe : error LGHT0001 : Exception of type 'System.OutOfMemoryException' > was thrown. > > Exception Type: System.OutOfMemoryException > > Stack Trace: >at System.String.CtorCharArrayStartLength(Char[] value, Int32 startIndex, > Int32 length) >at System.Xml.XmlTextReaderImpl.NodeData.get_StringValue() >at System.Xml.XmlTextReaderImpl.get_Value() >at System.Xml.XmlTextReader.get_Value() >at System.Xml.XmlValidatingReaderImpl.get_Value() >at System.Xml.Schema.BaseValidator.ValidateText() >at System.Xml.Schema.XsdValidator.Validate() >at System.Xml.XmlValidatingReaderImpl.ProcessCoreReaderEvent() >at System.Xml.XmlValidatingReaderImpl.Read() >at System.Xml.XmlValidatingReader.Read() >at Microsoft.Tools.WindowsInstallerXml.Field.Parse(XmlReader reader) >at > Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseTuple(Intermediate > intermediate, XmlReader reader, Section section, TableDefinition tableDef) >at > Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseTable(Intermediate > intermediate, XmlReader reader, Section section, TableDefinitionCollection > tableDefinitions) >at > Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseSection(Intermediate > intermediate, XmlReader reader, TableDefinitionCollection tableDefinitions) >at > Microsoft.Tools.WindowsInstallerXml.Intermediate.ParseIntermediate(Intermediate > intermediate, XmlReader reader, TableDefinitionCollection tableDefinitions, > Boolean suppressVersionCheck) >at Microsoft.Tools.WindowsInstallerXml.Intermediate.Load(XmlReader > reader, String path, TableDefinitionCollection tableDefinitions, Boolean > suppressVersionCheck) >at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) > > -- > View this message in context: > http://www.nabble.com/memory-usage-tf2774539.html#a7753597 > Sent from the wix-users mailing list archive at Nabble.com. > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] memory usage
Ok, but please help me in on doing that We decided to use includes because we have huge directory tree and some parts of the tree are in the main wxs file, and some are in the included xmls. We need to refer to the folders from the xmls to the wxs (for example at shortcut creation). And it is possible that in two different xml files we use the same directory. Maybe undersandable if i show you a sample. I'm sure that there can be lot of problems with the design, but we are not fully familiar with all parts of the wix. :( Still learning. Please tell me all problems that you find. First of all. We have different xmls for ComponentRefs and different for the Folders/Components. We needed this to be able to manage the files easily by scripts. We have more different users on the target PC, and we have to be able to install different shortcuts and permissions for the users. You can find some sample code below. Sorry for the long post, but i can not make is shorter. I'm waiting for all helps and comments. Thanks in advance Tamas The main wxs looks like this: Level="1"> POWER="MAN" Source="SourceDir\..." DiskId="1" Vital="yes"/> LongName="Start Menu"> LongName="Start Menu"> LongName="Scheduler.bat" src="SourceDir\.." DiskId="1" Vital="yes"/> LongName="poller.bat" src="SourceDir\.." DiskId="1" Vital="yes"/> *HOST.xml:* Source="..."/> Key="..." KeyPath="no" Name="Installed" Value="Installed" Type="string"/> Name="Tool1.lnk" LongName="Good Tool.lnk" Target="c:\Program Files\Internet Explorer\iexplore.exe" WorkingDirectory="c:\Program Files\Internet Explorer" /> LongName="Userblabla.exe" src="SourceDir\..." DiskId="1" Vital="yes"/> LongName="Userlonganemee.exe" src="SourceDir\..." DiskId="1" Vital="yes"> Directory="User2Startup" Name="Tool5.lnk" LongName="Good Tool5.lnk" WorkingDirectory="CompanySub"> Key="htmlfile\shell" KeyPath="no"/> KeyPath="no"/> Key="SOFTWARE\..." KeyPath="no" Name="File" Value="comments.txt" Type="string"/> *HOST_head.xml:* - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] memory usage
We have one wxs and many xmls with . These xmls contain the folders/files/registries. We have the UI in a different xml too. If we can manage the xml files to be smaller, that can speed up the candle? Rob Mensching wrote: Do you have just one gigantic XML file or are you splitting your product into many smaller .wxs files and letting the linker bring them back together? There is nothing special in the compiler. Normally it completes in seconds because there is very little IO. However, if you make one gigantic XML file then candle is probably spending all of its time slogging through the XmlDocument. *From:* TibTam [mailto:[EMAIL PROTECTED] *Sent:* Thursday, December 07, 2006 10:21 *To:* Rob Mensching *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] memory usage off topic: Sorry, i pressed Reply instaed of Reply All... on: You are right, light uses lot of memory. About 300-350 MB normally, but some said that on his machine it uses more than 500 MB. This sounds a bit strange to me, because he uses the same files and method to create the msi. Is this posibble? But out bigger problem is the CPU usage, what is made by candle.exe. Light uses about the same memory size that candle uses(bit more), but light does not use the CPU at 100% for all the time. Could you please help me to understand why candle uses the CPU at 100% for long minutes? (10-15-20 mins, depending on the machine) And what can we do to reduce this? (I mean to reduce the time while candle uses the CPU.) If i'll have time, i'll check the code for optimization, but i can't promise anything. :) Thanks Tamas Rob Mensching wrote: Please, keep the mailing list on all replies. I assume all your seeing the memory hit in the linker (light.exe), right? I haven't checked the memory usage in a while but your project is very large so that might be a very reasonable number right now. I don't think Office, VS, or SQL complain about the memory usage for their products because they probably all have at least a GB in all the machines and I'm not sure you'd immediately notice how much memory is being used. That said, if you wanted to profile the WiX toolset and found places where we could optimize our memory usage, that'd be really cool. *From:* TibTam [mailto:[EMAIL PROTECTED] *Sent:* Thursday, December 07, 2006 10:02 *To:* Rob Mensching *Subject:* Re: [WiX-users] memory usage Keywords="Installer" Description="Software installer" Comments="Copyright mycompany" Manufacturer="mycompany" InstallerVersion="100" Languages="1033" Compressed="yes" SummaryCodepage="1252"/> But the working scenario is the same if i set the compressed to No. (I do not know where can i check the compression level. :( ) Rob Mensching wrote: Are you compressing your files? If so, what compression level are you using? -----Original Message- From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of TibTam Sent: Thursday, December 07, 2006 09:36 To: wix-users@lists.sourceforge.net <mailto:wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] memory usage The result msi is 250MB. About 2500 files are being installed and more then 20 000 registry keys. We split the wix files into many parts. We have one wxs containing the projects and main folders, and many xmls. These xmls are included into the main wxs. Regards, Tamas Rob Mensching wrote: Uhh, maybe but you'd need to be a lot more specific about what in your project is "quite big". -Original Message- From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi Sent: Thursday, December 07, 2006 05:58 To: wix-users@lists.sourceforge.net <mailto:wix-users@lists.sourceforge.net> Subject: [WiX-users] memory usage Hi! We have a quite big project and wix uses huge amount of memory. (more than 500 MBs) Is there any possibility to maximize the memory usage? How does the package generation works? Thanks a lot Tamas - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV <http://www.techsay.com/default.php?page=join.php&p=sourceforge&am
Re: [WiX-users] memory usage
off topic: Sorry, i pressed Reply instaed of Reply All... on: You are right, light uses lot of memory. About 300-350 MB normally, but some said that on his machine it uses more than 500 MB. This sounds a bit strange to me, because he uses the same files and method to create the msi. Is this posibble? But out bigger problem is the CPU usage, what is made by candle.exe. Light uses about the same memory size that candle uses(bit more), but light does not use the CPU at 100% for all the time. Could you please help me to understand why candle uses the CPU at 100% for long minutes? (10-15-20 mins, depending on the machine) And what can we do to reduce this? (I mean to reduce the time while candle uses the CPU.) If i'll have time, i'll check the code for optimization, but i can't promise anything. :) Thanks Tamas Rob Mensching wrote: Please, keep the mailing list on all replies. I assume all your seeing the memory hit in the linker (light.exe), right? I haven't checked the memory usage in a while but your project is very large so that might be a very reasonable number right now. I don't think Office, VS, or SQL complain about the memory usage for their products because they probably all have at least a GB in all the machines and I'm not sure you'd immediately notice how much memory is being used. That said, if you wanted to profile the WiX toolset and found places where we could optimize our memory usage, that'd be really cool. *From:* TibTam [mailto:[EMAIL PROTECTED] *Sent:* Thursday, December 07, 2006 10:02 *To:* Rob Mensching *Subject:* Re: [WiX-users] memory usage Keywords="Installer" Description="Software installer" Comments="Copyright mycompany" Manufacturer="mycompany" InstallerVersion="100" Languages="1033" Compressed="yes" SummaryCodepage="1252"/> But the working scenario is the same if i set the compressed to No. (I do not know where can i check the compression level. :( ) Rob Mensching wrote: Are you compressing your files? If so, what compression level are you using? -----Original Message- From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of TibTam Sent: Thursday, December 07, 2006 09:36 To: wix-users@lists.sourceforge.net <mailto:wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] memory usage The result msi is 250MB. About 2500 files are being installed and more then 20 000 registry keys. We split the wix files into many parts. We have one wxs containing the projects and main folders, and many xmls. These xmls are included into the main wxs. Regards, Tamas Rob Mensching wrote: Uhh, maybe but you'd need to be a lot more specific about what in your project is "quite big". -Original Message- From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi Sent: Thursday, December 07, 2006 05:58 To: wix-users@lists.sourceforge.net <mailto:wix-users@lists.sourceforge.net> Subject: [WiX-users] memory usage Hi! We have a quite big project and wix uses huge amount of memory. (more than 500 MBs) Is there any possibility to maximize the memory usage? How does the package generation works? Thanks a lot Tamas - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> ___ WiX-users mailing list WiX-users@lists.sourceforge.net <mailto:WiX-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] memory usage
The result msi is 250MB. About 2500 files are being installed and more then 20 000 registry keys. We split the wix files into many parts. We have one wxs containing the projects and main folders, and many xmls. These xmls are included into the main wxs. Regards, Tamas Rob Mensching wrote: > Uhh, maybe but you'd need to be a lot more specific about what in your > project is "quite big". > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi > Sent: Thursday, December 07, 2006 05:58 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] memory usage > > > Hi! > > We have a quite big project and wix uses huge amount of memory. (more than > 500 MBs) > Is there any possibility to maximize the memory usage? > How does the package generation works? > > Thanks a lot > Tamas > > > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
