Has there been any reply to this post?
I have the exact same issue of hanging-at-99% window saying "Adding functions to filenames". The only few occasions when it did work were for some function calls with extremely low timer samples (the least interesting case).
My system is Windows XP SP3 and I use CodeAnalyst 3.2.962.731
This happens both when using CodeAnalyst as a standalone and from Visual Studio 2008.
It happens both with Debug code and ReleaseWithDebugSymbols.
It's really frustrating because it's a really convenient and easy to use product.
Thanks in advance.
I have a few questions. Is this managed code? Are there intrinsic functions? Have you enabled an enhanced instruction set (/arch:)? How large is the module? Is there anything unusual about the module? What is your system's memory usage like when it hangs?
Does it still have issues if you uncheck "Show code density chart" in the Tools | CodeAnalyst Options dialog, Toolbars tab?
Thank you for replying quickly.
> Is this managed code?
Just Debug with /ZI
> Are there intrinsic functions?
Not explicitly enabled, unless they're enabled by /O2 (which is set)
> Have you enabled an enhanced instruction set (/arch:)?
> How large is the module?
> Is there anything unusual about the module?
Well... I don't think so. It just uses CUDA. (sorry :) )
> What is your system's memory usage like when it hangs?
CPU usage (on a quad core) goes from 5% to 30% and "CodeAnalyst.exe" process memory usage goes from about 30Mb, and it increases very slowly (at about 200kb/s) to ???? It has just passed 800Mb now and is still growing. I'm going to have to kill the process (it's been hanging for a couple of hours now).
> Does it still have issues if you uncheck "Show code density chart" in the Tools | CodeAnalyst Options dialog, Toolbars tab?
Yes it still happens.
I hope those answers will help.
Update on the memory usage: i let the above process run overnight and this morning, it had reached 1.9Gb of RAM and had stalled at that stage. I had to exit it.
I think we found the issue. We found similar symptoms when the symbolic information reported a source line way, way outside the source file. The next version (coming out soon) will have a fix.
Thanks for your help and patience,
That's good news. Thanks for getting back on that. Would that be possible to be notified when the next version is released?