I did not see any way to resolve this crash. Until there is a pattern, I don't see a way to fix it. So, my suggestion would be to avoid using this member entirely and, instead, use the "TextVector" MEMBER of the examineitemwindow datatype:
December 19, 2006 -- By Amadeus
[ISXEQ2-20061215b.exe]
* Added the following new MEMBERS to the 'examineitemwindow' datatype:
1. TextVector (int type) [ Number of "Texts" in the TextVector ]
2. TextVector[#] (eq2uielement type) ['text' eq2uielement type]
So, for each item you would need to "examine" it so that the window opens, and then use ${ExamineItemWindow.TextVector} to get the information you want.
To be honest, this may be the only way to safely get the information. The method that I use for "ExamineText" is hackish and not anticipated by the client, so that's probably why it's not stable. (The client doesn't really need to know the examinetext except for *in* an ExamineItemWindow.)