VisualFormat crash in msvbvm60.dll (TST5.5.2)

We are seeing very frequent crashing when using VisualFormat under the browser-based Templating on 5.5.2. We run are upgrading to TS 5.5.2 and TST 5.5.2. Anyone else seeing better results? I have a case open with Interwoven, but response seems slow to most VF issues, as info moves between Interwoven and Ektron....

Clients are typically on Windows 98 with IE 5.5/5.5sp2. I've also had it crash on Windows 2000 with IE 5.5sp2.

Typical DCTs include four text areas with Visual Formatter active. Visual Formatter version shows '2.5.0.15'. The crash occurs when closing or saving the DCT. Results thus far are inconsistent, but the crashes seem to occur more frequently the longer the templating client is used. In one instance a DCT was simply left open on screen for 30 minutes with not changes made, and when it was closed, IE crashed. Here is some typical output from the crash error report from IE 5.5:

Error Details: Internet Explorer has encountered an internal error.
Error Signature:
AppName: iexplore.exe AppVer: 5.51.4807.2300
ModName: msvbvm60.dll ModVer: 6.0.88/77
Offset: 0002b83c

Find more posts tagged with

Comments

tvaughan

Yeah, I've seen crashes on our VF-enabled templates, too.

We use TS 5.0.1 and our clients are W2K with IE 5.5.

When crashes do happen, it seems to be on templates with many textareas and especially if there are multiple "daughter windows" open. By "daughter windows" I mean if you click on the "Preview" button of a DCT and it pops up a little window asking which TPL you want to preview your DCR in. If you leave that window open and/or the "Save As" window, etc., I think your chances of crashing increase.

Tom

anilp

The crash could be due to the high number of VisualFormat-enabled textareas in the form. The VisualFormat is an activeX control that gets run within the browser memeory, and will tax the client computer resources for each textarea it is opened.
Please be careful about VF-enabling the textareas within a replicant.
The best solution is to open the VF editor in a daughter window. If you are using 5.0.1, please refer to KB article 2417. In you are using 5.5.2, you can specify whether the VF is available 'inline' with the form or as a callout. Please refer to the templating documentation.

the snippet of templating DTD in 5.5.2 is as follows -
<!ELEMENT textarea (allowed?,callout?,java-callout?,cgi-callout?, default?) >
<!ATTLIST textarea
required (t|f) "f"
rows CDATA "0" cols CDATA "0"
wrap (off|virtual|physical) "off"
validation-regex CDATA #IMPLIED
rtf (t|f) "f"
line-break (P | BR) #IMPLIED
external-editor CDATA ""
external-editor-config CDATA #IMPLIED
external-editor-inline (t|f) "t"
>

Migrateduser

Anil, thanks very much, that's a response I had not gotten from Interwoven Support yet. The Templating Developer Guide does not indicate that the inline attribute is TRUE by default...the text on pg 60 seems to indicate that you'll see a button for VF unless you include external-editor-inline="t".

We are experimenting on one template with VF set to a button, and we have seen no crashes so far. This looks like the proper work-around.

There obviously need to be more guidance in the docs regarding the use of VF....

brent1

Unfortunately, I could not read the KB article mentioned (2417). When I try I get:

***********************************************
Access denied to Article 2417
This article has restricted access.

Click here to return to the knowledge base.
***********************************************
Why secrets, why?

Brent Seddelmeyer
Beckman Coulter Inc.

tvaughan

I got turned away at the gates, too.

I guess that "Interwoven Internal" docs are listed in the Knowledge Base just to tease us non-Interwoven internal people.

Tom

anilp

i work for interwoven. the reason 2417 is not visible to you is that the content in it is applicable only to 5.0.x, and not forward-compatible - thus it is not generally available.

so please pardon my wrong guidense.

Migrateduser

You can use external-editor-inline in TST 5.0.2 or 5.5.2

If someone else reading this is using <5.0.2, I'd check with
support and ask them to help you and give them the internal
KB article number.

VF is usually inline if using IE browser, and not if using NS
(the reason they are different is because of how activeX
is handled.)

It sounds like setting this to false has helped your problem,
which is great.

Jason Heirtzler
Interwoven Engineering

Edited by jheirtzl on 08/06/02 02:11 PM (server time).

kwoo

We are using TS 5.5.2 with IE5.5 SP2 on Win2K Pro. I notice my browser crashes after I installed VisualFormat. We have many textareas with VF-enabled. In the DCT, we do something like this: <textarea rows="10" cols="64" wrap="virtual" external-editor="visualformat"/>. VF not only slows down my PC when opening a single DCR, but crashes my browser when closing or saving the DCR. Please help.
Is there a way to uninstall Visual Format?

MartinAtCitat

Any news on this mysterious KB article 2417?

Best Regards
Martin

Citat Solutions AB
Stockholm, Sweden

Migrateduser

I'm checking with Support to see if the information in that KB article is OK to post here. The document is currently company confidential.

mogoo

any word yet on that article? We're on 5.0, and there are content providers that have crashing computers...
thanks,
maureen