[wix-users] heat.exe System.OutOfMemoryException help

Hoover, Jacob Jacob.Hoover at greenheck.com
Wed Jul 13 15:08:39 PDT 2016 

Hmm,
  I am able to run heat against a deployment with over 32k files and I don't get an out of memory exception.  What options are you passing to heat? (I also use the task not the command line.)


    <HeatDirectory NoLogo="true" ToolPath="$(WixToolPath)" VerboseOutput="true" AutogenerateGuids="true"
     GenerateGuidsNow="false" OutputFile="$(IntermediateOutputPath)All.wxs"
     SuppressFragments="true" Directory="$(A_OUTPUT_DIR)\Data\" ComponentGroupName="ProductComponents"
     DirectoryRefId="CommonData" PreprocessorVariable="var.SourceDataFolder" SuppressCom="true" SuppressRootDirectory="true" SuppressRegistry="true"
     Condition =" '$(UpToDate)' != 'Equal' "/>

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Farrukh Waheed
Sent: Wednesday, July 13, 2016 1:56 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] heat.exe System.OutOfMemoryException help

Just to give you an idea, I once had to add files during build like you are doing and I used xml transforms (*.xslt) with Heat task which was modifying Components by specifying Feature to be associated.



On 13 July 2016 at 11:33, Shintaro Takechi <devst119 at gmail.com> wrote:

> Ok thanks to you, I was able to complete the task by running for loop 
> for each directories within the targetdirectory with command lines to 
> solve the problem of OutOfMemory exception.
> However, this solution means I have to update the core wxs file to add 
> new componentgroup as they come up (when new directory is added) Would 
> there be some solution that allows me to not modify core wxs file?
>
> On Wed, Jul 13, 2016 at 10:33 AM, Shintaro Takechi 
> <devst119 at gmail.com>
> wrote:
>
> > > Farrukh
> > Thank you for the suggestion. I have tried executing it via batch 
> > file but same error. (but seems like different stack trace)
> >
> > heat.exe : error HEAT0001 : Exception of type 
> > 'System.OutOfMemoryException' was thrown.
> >
> > Exception Type: System.OutOfMemoryException
> >
> > Stack Trace:
> >    at
> >
> Microsoft.Tools.WindowsInstallerXml.Serialize.ElementCollection.Sequen
> ceItem..ctor(Type
> > elementType)
> >    at Microsoft.Tools.WindowsInstallerXml.Serialize.Fragment..ctor()
> >    at
> >
> Microsoft.Tools.WindowsInstallerXml.Extensions.UtilMutator.MutateCompo
> nents()
> >    at
> > Microsoft.Tools.WindowsInstallerXml.Extensions.UtilMutator.Mutate(Wi
> > x
> wix)
> >    at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
> >    at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] 
> > args)
> >
> > On 7/13/16, Farrukh Waheed <farrukh1 at gmail.com> wrote:
> > > Did you try to execute the same Heat command line from Command 
> > > Prompt (Admin mode) for same directory? May be you want to close 
> > > Visual studio
> > and
> > > simply generate the .wxs file and see if it is crashing in Command 
> > > prompt...
> > >
> > > On 13 July 2016 at 09:48, Shintaro Takechi <devst119 at gmail.com> wrote:
> > >
> > >> Since this command is running in visual studio pre-build event, I 
> > >> am
> not
> > >> even at the point to make separate msi packages.
> > >> May be I will robocopy each subdirectories in separate location 
> > >> of
> local
> > >> drive and output them in different wxs.
> > >> I guess my next step is to research how to use robocopy well?
> > >>
> > >> This command line call to heat is just copied from what 
> > >> HeatDirectory generated for me.
> > >> The reason I am using command line version over HeatDirectory is
> because
> > >> I
> > >> had to insert robocopy to copy files in my local drive.
> > >>
> > >>
> > >> On Wed, Jul 13, 2016 at 9:40 AM, Phill Hogland <
> > phill.hogland at rimage.com>
> > >> wrote:
> > >>
> > >> > >>What would be the best approach to harvest in smaller sections?
> > >> >
> > >> > I have seen before the recommendations to create a bundle and 
> > >> > drive multiple MSI packages.  I don't have the expertise to say 
> > >> > that is
> the
> > >> > "best" but it has worked very well for my projects.  I have 
> > >> > also
> seen
> > >> > the
> > >> > recommendation to be careful when using heat.exe and check the 
> > >> > resulting output carefully.  So I do have several MSI projects 
> > >> > that make use
> of
> > >> > HarvestDirectory target, which I greatly prefer over any 
> > >> > command
> line
> > >> call
> > >> > to heat.
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> >
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HarvestD
> irectory-target-for-multiple-directories-td7596917.html
> > >> >
> > >> >
> > >> > ________________________________
> > >> > From: wix-users <wix-users-bounces at lists.wixtoolset.org> on 
> > >> > behalf
> of
> > >> > Shintaro Takechi <devst119 at gmail.com>
> > >> > Sent: Wednesday, July 13, 2016 11:27:35 AM
> > >> > To: WiX Toolset Users Mailing List
> > >> > Subject: Re: [wix-users] heat.exe System.OutOfMemoryException 
> > >> > help
> > >> >
> > >> > > Phill
> > >> > What would be the best approach to harvest in smaller sections?
> > >> > I still would like to enjoy the automatic file gathering of
> heat.exe.
> > >> > I currently have 32GB of memory, but would getting bigger 
> > >> > memory
> help?
> > >> > I feel like as files are getting larger, the problem will persist.
> > >> >
> > >> > On Wed, Jul 13, 2016 at 9:17 AM, Phill Hogland 
> > >> > <phill.hogland at rimage.com
> > >> >
> > >> > wrote:
> > >> >
> > >> > > >>The size of whole folder that I am trying to include comes 
> > >> > > >>out
> to
> > >> > > >> be
> > >> > > 8.56GB
> > >> > > with 17220 files and 1589 folders.
> > >> > > >>Would anybody know the solution for this?
> > >> > >
> > >> > > Harvest smaller sections.
> > >> > > Get more memory.
> > >> > >
> > >> > >
> > >> > >
> > >> > > ________________________________
> > >> > > From: wix-users <wix-users-bounces at lists.wixtoolset.org> on
> behalf
> > of
> > >> > > Wheeler, Blaine (DSHS/DCS) <BWheeler at dshs.wa.gov>
> > >> > > Sent: Wednesday, July 13, 2016 11:14:48 AM
> > >> > > To: WiX Toolset Users Mailing List
> > >> > > Subject: Re: [wix-users] heat.exe System.OutOfMemoryException 
> > >> > > help
> > >> > >
> > >> > > How many files are you trying to harvest?  Heat can handle an
> awful
> > >> lot.
> > >> > >
> > >> > > Could you share the heat command in your next post to this list?
> > >> > >
> > >> > > -----Original Message-----
> > >> > > From: wix-users 
> > >> > > [mailto:wix-users-bounces at lists.wixtoolset.org]
> On
> > >> > Behalf
> > >> > > Of Shintaro Takechi
> > >> > > Sent: Wednesday, July 13, 2016 8:39 AM
> > >> > > To: WiX Toolset Users Mailing List
> > >> > > Subject: Re: [wix-users] heat.exe System.OutOfMemoryException 
> > >> > > help
> > >> > >
> > >> > > Right. It is network drive. Hence in the second example I 
> > >> > > first execute the robocopy to copy to my local drive and 
> > >> > > tried the heat. But got same
> > >> > out
> > >> > > of memory exception...
> > >> > >
> > >> > > Get Outlook for iOS
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Tue, Jul 12, 2016 at 10:20 PM -0700, "Farrukh Waheed" < 
> > >> > > farrukh1 at gmail.com> wrote:
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > What do you mean by "files on the network" ?
> > >> > >
> > >> > > On 13 July 2016 at 04:37, Shintaro Takechi  wrote:
> > >> > >
> > >> > > > files on the network
> > >> > >
> > >> > >
> ____________________________________________________________________
> > >> > > WiX Toolset Users Mailing List provided by FireGiant 
> > >> > > http://www.firegiant.com/
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> ____________________________________________________________________
> > >> > > WiX Toolset Users Mailing List provided by FireGiant 
> > >> > > http://www.firegiant.com/
> > >> > >
> > >> > >
> ____________________________________________________________________
> > >> > > WiX Toolset Users Mailing List provided by FireGiant 
> > >> > > http://www.firegiant.com/
> > >> > >
> > >> > >
> ____________________________________________________________________
> > >> > > WiX Toolset Users Mailing List provided by FireGiant 
> > >> > > http://www.firegiant.com/
> > >> > >
> > >> >
> > >> > _______________________________________________________________
> > >> > _____ WiX Toolset Users Mailing List provided by FireGiant 
> > >> > http://www.firegiant.com/
> > >> >
> > >> > _______________________________________________________________
> > >> > _____ WiX Toolset Users Mailing List provided by FireGiant 
> > >> > http://www.firegiant.com/
> > >> >
> > >>
> > >> _________________________________________________________________
> > >> ___ WiX Toolset Users Mailing List provided by FireGiant 
> > >> http://www.firegiant.com/
> > >>
> > >
> > > __________________________________________________________________
> > > __ WiX Toolset Users Mailing List provided by FireGiant 
> > > http://www.firegiant.com/
> > >
> >
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant 
> http://www.firegiant.com/
>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-users mailing list