In particular, if all of the calls that you're making got attributed to code 
in Base, that could explain what you saw. Inlining could also be a source of 
confusion. The most accurate way to do this kind of analysis is only available 
in julia 0.4:

    julia --inline=no --track-allocation=user

--Tim

On Tuesday, January 06, 2015 02:59:11 PM Petr Krysl wrote:
> Actually, correction: for 0.3.4 the _system_ *.mem files are in the julia
> folders. For _my_ source files the .mem files cannot be located.
> 
> P
> 
> On Tuesday, January 6, 2015 2:15:02 PM UTC-8, Petr Krysl wrote:
> > I did this as suggested. The code  executed as shown below, preceded by
> > the command line.
> > The process completes,  but there are no .mem files anywhere. Should I ask
> > for them specifically?
> > 
> > # "C:\Users\pkrysl\AppData\Local\Julia-0.4.0-dev\bin\julia.exe"
> > --track-allocation=all memory_debugging.jl
> > cd( "C:/Users/pkrysl/Documents/GitHub/jfineale"); include("JFinEALE.jl");
> > include("examples/acoustics/sphere_scatterer_example.jl")
> > Profile.clear_malloc_data()
> > include("examples/acoustics/sphere_scatterer_example.jl")
> > quit()
> > 
> > On Tuesday, January 6, 2015 1:50:11 AM UTC-8, Milan Bouchet-Valat wrote:
> >> Le lundi 05 janvier 2015 à 20:48 -0800, Petr Krysl a écrit :
> >> > Hi guys,
> >> > 
> >> > How does one figure out where allocation  of memory occurs?   When I
> >> > use the @time  macro it tells me there's a lot of memory allocation
> >> > and deallocation going on.  Just looking at the code I'm at a loss: I
> >> > can't see the reasons for it there.
> >> > 
> >> > So, what are the tips and tricks for the curious?  How do I debug the
> >> > memory allocation issue?  I looked at the lint, the type check, and
> >> > the code_typed().  Perhaps I don't know where to look, but  these
> >> > didn't seem to be of much help.
> >> 
> >> See this:
> >> 
> >> http://docs.julialang.org/en/latest/manual/profile/#memory-allocation-ana
> >> lysis
> >> 
> >> (Would probably be good to backport to the 0.3 manual...)
> >> 
> >> 
> >> Regards

Reply via email to