Clicking "Close" on DCT causes IE to close

I'm absolutely stumped on this one. We have a DCT that, upon closing, should submit the DCR to a workflow (tt_data specified in available_templates.cfg). However, when this template is used at one our sites, clicking close causes IE to shutdown entirely. The user is not prompted to submit the file to approval and there is no error. Maybe 1% of the time the user will actually be prompted to submit the file for approval. Has anyone ever seen anything like this? Any ideas on what to check?

Find more posts tagged with

Comments

Michael

A question and a suggestion:

When you say that IE closes down entirely do you mean all open windows of IE; not just the current templating window close?

The tt_data workflow won't be fired if the DCR is already attached to a workflow -- you can check this in File->File Properties

Lex

Thanks for the response, Michael. Only the IE windows associated with TeamSite close. That is, the TeamSite launch window, the TeamSite webdesk pro window, and the DCT window all close. Any other IE windows that happen to be open are unaffected. This is just too weird.

The DCR in question is not associated with any other workflow when this happens.

JonathonG

Well, that behavior makes sense if something in the JavaScript is causing the browser to crash. More than likely, all of the TeamSite windows are running in the same process, while the other browser windows are not.

So, it would seem that something about the way TST is trying to bring up the prompt is crashing the browser. A couple of things to check:

Are the browser versions the same between the one that crashes and the one that doesn't?
Are the settings the same?

Jonathon
Independent Interwoven Contractor

Lex

OK, I've been able to duplicate the error here. All IE versions and settings are the same (although this is probably moot since I can duplicate the problem). The error is inconsistent, that is, sometimes I can edit a DCR and submit it to workflow just fine. Other times I get an Application Error as follows:

SysFader: iexplore.exe - Application Error

The instruction at "0x7344b498" referenced memory at "0x03fd8628". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

However, if I use an alternate browser (I use SlimBrowser which is why I erroneously assumed the error was only occurring at this particular site) the error doesn't occur. And from searching Google it appears as if SysFader has something to do with menu transitions and page transitions in IE, however page transitions are disabled. Unfortunately I can't dictate that a different browser than IE be used since IE is our corporate standard. My Google searching hasn't turned up a reliable method to stop this from happening, though.

Lex

OK, I was able to solve the problem after referencing this post in another thread:

http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=NEWSGROUPS_GENERAL&Number=164&page=&view=&sb=&o=&vc=1#Post164

It appears as if the inline ActiveX control for the Visual Format Editor is causing the problem because as soon as I changed them to no longer be inline (we have 4 VFEs on this template) the problem went away. I consider this a temporary fix as I'd still like to know why IE chokes on the inline ActiveX controls.

ela

Hi, this sounds like the famous "browser crash problem" which you'll find described in various threads in this forum, e.g. Re: More DCT crashes! argh!
As far as I understand, it's usually caused by the browser running out of available memory.

In TeamSite 6 you'll only get one visualformat editor active at a time, which should solve the problem.

As we will probably stick to TS 5.5 for a while, I have created a templating form with one big textarea field with the vf editor, and converted many of the old dcrs to fit in the new form.

Migrateduser

Anyone have any tips on how to get rid of the crash if you are not using Visual Format? When users close a DCR on our system its always a random gamble - Will it crash? will the submit dialog come up ? You never now. We've had this problem for so long that our users think its an exciting feature :-) (5.5.2, W2K - W2K/XP IE 6)