Memory

[Bill O'Neil]

I'm new to Just Trace and profiling in this manner and general - but I'm trying to track down some odd memory usage in an ASP.NET Website project & I'm having difficulty.  I can run the Memory Profiler - and it gives me some potential leaks (Objects w/ small "own" size and large "retained" size) but when I examine them I have no way of telling where these objects originate.  "System.Object" is all I get.  Is there any way to extract more information or detail?

[Mihail]

Hello Bill,

Currently JustTrace detects all static fields as System.Object and does not show where the object were allocated. The next JustTrace release (Q3 2012) will have improvements:

• it will be possible to see the allocation call site
• it will be possible to see the field name which holds the object
• it will show the GC root type - static field, thread stack, GC handle, pinned object, etc.

As an immediate solution I would suggest to create two snapshots and compare them. If you have knowledge about the app you can see if they are increasing objects of a given type and decide whether they are leaks or not.

Please don't hesitate to ask if you have further questions.

Greetings,
Mihail
the Telerik team

[Bill O'Neil]

It seems that:

• it will be possible to see the allocation call site
• it will be possible to see the field name which holds the object

would give me just what I need.  Does Just Trace ever release beta versions (like the .NET controls) - or are we looking at an "end of 2012" window for this functionality?

One additional (tangentially) related item - the global Just Trace stats - that give the "# of exceptions" - is there any way to drill down and see where those exceptions lie?

Thanks!
Bill

[Mihail]

Hi Bill,

Thank you for your questions. JustTrace complies with the company policy to release so called "internal builds" on a regular basis. Actually the last internal build 2012.2.806.9 was released yesterday. We strive to release an internal build every two weeks.

I guess you are interested in the particular features we discussed in this thread. These features are planned for Q3 2012 which is scheduled for 17th of October. Probably they will be first available 2 or 3 internal builds (4 or 6 weeks) before the official Q3 2012 release.

As for the actual exception stack (the call stack where the exception is thrown) - many customers want this feature and it is already on our task list. We probably will ship it with Q3 2012 release.

Regards,
Mihail
the Telerik team

[Bill O'Neil]

Any of these items in the internal build yet?  Thanks!
Bill

[Todor]

Hi Bill,

We are working on showing the member names and the feature should be available in one of our next internal builds.

As for the other features, they most probably will be pushed for after the 2012 Q3 release.

Regards,
Todor
the Telerik team

[Bill O'Neil]

were any of these in the Q3 release?  Thanks!  Bill

[Todor]

Yes, the Q3 release shows member names. Feel free to download it and check all the new goodies in it.

Kind regards,
Todor
the Telerik team

[Bill O'Neil]

Just checking in - does JustTrace allow you to view the Exceptions shown?  I keep seeing Exceptions logged - even though I don't see any while using the app.  I'd love to figure out what Just Trace is seeing.
Thanks,
Bill-

[Kaloyan]

Hi Bill O'Neil,

Thank you for contacting Telerik support.

With the current version of JustTrace, you can only see the number of all the exceptions thrown inside your program. I have attached a screenshot to show you this functionality.

On that screenshot, I have profiled JustTrace with JustTrace. As you can notice there are 399 exceptions thrown. These are all handled exceptions from the base class library along with the handled exceptions in JustTrace.

I hope this answers your question.

Further, would you like to see feature that shows/filters the handled exceptions in your program (excluding the ones thrown by the BCL) in JustTrace?

Regards,
Kaloyan
Telerik

[Bill O'Neil]

When you say:

These are all handled exceptions from the base class library along with the handled exceptions in JustTrace.

How do you know this?

And yes - I'd love something that would let you see the exceptions (and I think it was noted as a common request in the 8/7/12 message in this thread.)

Thanks!
Bill

[Kaloyan]

Hello Bill O'Neil,

If an exception is not caught, it will crash your application. In my case, if there were any unhandled exceptions, a dialog box would have appeared (with the exact exception lead to the failure) and then my program would have crashed. That is why, I assume all of the exceptions shown, are somehow handled in the running code.

Unfortunately, we won`t be able to release such feature with the major JustTrace 2013 Q2 release this week. However, there is good chance for it, to be shipped with any of the upcoming Service Packs / Internal Builds during the next Q.

Regards,
Kaloyan
Telerik