I have been working on this and I think I have cracked two thirds of the problem.
on another forum post I found a method of clearing the c strings when they got too big.
A C string is a NULL terminated array of chars.
NULL,a,a,a,a,a,a,a,a,a,a,,a,a,a,a,a,a is a 0 length string. As is
NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL
More than one NULL is like more than one stop sign on a post.
Before I had three Strings and now I only have one
You'll be a lot better of with ZERO.
As the code takes roughly three times as long to crash now I suspect this getString function from textFinder is responsible.
The getString() function, despite the capital S, does not use Strings. Is 141 characters a reasonable number of characters? If the tweet to make coffee is considerably shorter than that, make tweet a lot smaller.
I do not really know how to approach this method. An example would be welcome.
You quoted one, and you have access to the source for the TextFinder library that uses char arrays to look at. I'm not sure what else to suggest.
char makeCoffee[15] = "make me coffee";
Psst. The compiler can count.