Thank you for your interest.

I believe it IS widely happening, I have seen this behavior reported on the DNN forum and it seems to be chalked up to a Web Farm or Caching. Changing something on the site moves the memory around and it may appear to have fixed the problem, but it may only be masking the real underlying issue. These types of issues are old hat to us old time C programmers. Depending on the random memory contents after the null terminator, this may happen more, less, or not at all, hence the appearance that there is no defect.

I have a binary trace and every time there is anything after the null terminator, the page has random results. This was very difficult to track down and I think most people just don’t notice it, give up, or accept the erroneous explanations. In fact, you can’t even see the issue because the characters happen after the null terminator, it can only be revealed in a trace.

This is also a bug in IE, IE should ignore anything after the </HTML> tag like all other browsers.

You can go to my test site, but you must be running IE 8, I think this also happens in IE7 but I can’t remember. It may even be related to IE 8 on Windows 7. But it definitely requires a combination of the two bugs, first DNN generating the extra chars, and then IE incorrectly dealing with them.

http://ilmason.org.sunflower.arvixe.com

Pick a page and keep clicking on the link, it is more frequent when clicking on the same link as opposed to reloading the page. It may take 15 different clicks, but it will eventually happen. Something going from one page to another, back and forth, will bring it faster.

We think alike, I changed the skin and it seemed to work for an hour and I thought “That’s it”, then it started happened again.

I have seen this on a different host, I even switched hosts hoping it was the providers problem.

The solution to this is either DNN must null terminate all characters in the buffer to the end, or send only the buffer up to the null terminator. Getting Microsoft to acknowledge their bug or fix IE is futile.

Awesome, I would greatly appreciate that. Very nice product, if I can get this fixed, the organization wants to go with the pro version to get the approval feature.

BTW, you may want to upgrade to the latest Telerik control DLL, I finally got them to prioritize and fix that annoying bug when dragging the editor size bar beyond the browser border. If you have never seen this, try it, it’s a colossal bug, and funny now that it’s fixed. Great controls, another good company.

Thanks again, take care…