The Finder crashes

[GB, author of iNMR]

I would have liked to comment on the newest version of iNMR (3.3.4),
but...

Today I have reported a bug to Apple and to the spotlight-dev mailing
list too. The detals are reather technical, but the result is easy to
see. If, working with the Finder of OS 10.6.2, I open a "Get Info"
window for an iNMR document (file name = plist.inmr) AND the section
"More Info" is disclosed, the Finder crashes. The spotlight plugin has
basically remained the same since its creation in 2006. Do you suffer
from the same bug?

Here is what I wrote to the Apple mailing list:

http://lists.apple.com/archives/spotlight-dev/2009/Nov/msg00001.html

In 2006 I wrote a Spotlight plug-in. It has being working great with
Tiger and Leopard. With the latest version of Snow Leopard 10.6.2 the
Finder crashes because of my plug-in. I can recompile this plug-in,
but it must remain compatible with 10.4. I have discovered that the
cause of the crash is a single attribute, which is an array of
floating numbers (from 1 to 3 items) and is displayed into the "Get
Info" windows of the Finder.
Actually the plugin "per se" always works. For example, with the
Terminal command:

arch -i386 mdimport -g path/to/plugin -d2 path/to/file

The plugin continues to function very well, as it always did. I get my
list of numbers and they are all correct.
The only difference is that I have added "arch -i386" at the beginning
of this command (my plugin is 32 bits).

What doesn't work is Spotlight itself, as revealed by the command:

mdls path/to/file

Now the list contains 5 numbers instead of 3 or 3 and only the first
number is correct. The problem is absent when the array contains a
single item.
For this kind of problem at least there is a work-around: I create
CFNumbers of kCFNumberSInt32Type instead of kCFNumberDoubleType.
Everything works fine, until I try to open the Get Info window of the
Finder for my file. The Finder crashes. If I rewrite my plug-in in a
way that this attribute disappears, everything works. A possible
solution would be to store the attribute as an array of strings, but I
would lose the ability of searching it as a value.
A better solution would be to make the attribute not displayable.

Do you think it can be a bug into Spotlight that will be fixed into a
future release of Snow Leopard? In this case I could wait and do
nothing.