[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Bizarre problem with MSXML4 that doesn't happen in MSXML3

---

---

I'm guessing it's the same problem - just boolean() causing the problem....
Try doing the same, such as boolean(/object/securityacl/text())

See if that works...

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Josh Twist
Sent: 11 April 2003 16:16
To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] Bizarre problem with MSXML4 that doesn't happen in MSXML3


Has anybody else ran into problems with MSXML4 crashing intermittently when
transforming certain XSL templates?

We've trawled the lists and we can't find anything that matches our problem
(including this post with a similar problem:
http://www.biglist.com/lists/xsl-list/archives/200208/msg00029.html; but we
aren't using the number() function at all).

It only happens with certain templates and will crash about 1 in every 7
runs (though it is entirely random).

We're using the Xselerator product and that bails out with the following
error "Access violation at address 69B219E9 in module 'msxml4.dll'. Read of
address 00000000"

We've also written a test VB app to repeatedly transform the XSLT and that
crashes leaving the following in the event log: "Faulting application
testxml4.exe, version 1.0.0.0, faulting module msxml4.dll, version
4.10.9404.0, fault address 0x0003fae7"

Neither have a problem if we transform using MSXML3 but we don't want to go
back to this as 4 runs rings around it speed-wise.

We're still not sure what is causing it, though we have noted that
commenting out the code below stops it crashing:

<xsl:variable name="objacl">
<!--
	COMMENT THIS OUT AND IT DOESN'T CRASH
	<xsl:choose>
		<xsl:when test="count(object/data/row) > 0">
			<xsl:value-of
select="/object/data/row[1]/field[@ref='f1']"/>
		</xsl:when>
		<xsl:when test="boolean(/object/securityacl)=true">
			<xsl:value-of select="/object/securityacl"/>
		</xsl:when>
		<xsl:otherwise>00000000</xsl:otherwise>
	</xsl:choose>
-->
</xsl:variable>

This is particularly strange as this code is used in other templates that
don't crash (and the resulting variable is used in other templates in just
the same way). Additionally, commenting out some different bits of code can
also stop the crash though again, there seems to be no pattern or logic to
what will and won't crash it.

This feels like we're chasing rainbows. The crash is intermittent and we
can't chase it down or isolate it. Any ideas?

Apologies if this problem has been covered before but we'd sure appreciate a
link to any related discussion!

Regards

Josh


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

---