Stack Overflow exception on specific pages

[ChristopherBass]

I have two sites on which I've installed Glimpse WebForms 1.0.1. On certain pages, Glimpse consistently throws a Stack Overflow exception. The exception goes away and the page loads properly, if I add "ControlTree" to the IgnoredTypes list.

I'm not sure what sort of tracing information would be most useful - please advise.

The sites are both running NET 4.0.30319.18052 (32 bit) in Microsoft-IIS/7.5 on Microsoft Windows NT 6.1.7601 Service Pack 1 (64 bit)

Log from a working page:
http://pastebin.com/YfLaVQsu
Log from a broken page:
http://pastebin.com/N1KrSnpm
Log from the same broken page, with the ControlTree disabled via the web.config, Tabs.ignoredTypes (The exact same set of log entries is what happens when I run the working page with the ControlTree disabled - so maybe not useful)
http://pastebin.com/Ny0uXGJN

[danjagnow]

This may be a duplicate of #598.

[ChristopherBass]

Could be - is there a good way to export my viewstate for a page, so we can see if there's anything unusual about it?

[CGijbels]

Could you try the latest WebForms NuGet package which includes the fixes made by #598 and see if that one solves your problems?

[ChristopherBass]

Is that just Glimpse Webforms 1.0.1? (With Glimpse ASP.NET 1.5.0 and Glimpse Core 1.7.0)
If so, that's what I'm already running.
Downloading now though, will let you know.
EDIT: Yep, NuGet's reporting it's already the one installed.

[CGijbels]

Yep it is the same version but has different content
We only update the version when we release a package, so you'll need to uninstall the previous one and then use this one (add it to a private local NuGet source)

[ChristopherBass]

Yep, that appears to be working. Excellent! Thank you.
As a note, when I unintalled and reinstalled, it created a second "glimpse" section and new httphandlers/etc, all with an 'xmlns="" ' attribute, rather than picking up the existing ones. That's probably because my web.config is largely within location tags, but the "glimpse" section at the end of the file wasn't in a location tag - so not sure why that happened.
Should I create a separate ticket for that? Easy enough to avoid by just backing up my web.config before running the install.

[CGijbels]

I'm glad the other build solved your issue, we'll try to release is it as soon as possible

The config issue sounds more like a NuGet issue, but if you can reproduce it, feel free to create a new issue for it and we'll see what we can do