Extractor causing 500 internal error

Hi,

There is a silly bug thats causing the parser with extractor with terms to throw a 500 error. I was pursuing a memory bug and even switched to a test machine with 4GB RAM and allowed it to run with 3GB RAM and still wouldn't import. Then, I rebuilt an entire server with a Vanilla LAMP install and could not get it to work either.

In the end, I simply switched parsers and started running again. What I'm not sure of its shooting blanks when it comes to importing nodes without terms (hence assuming that there is an error) or the extractor itself is broken.

I could not get an error on Apache logs or Watchdog, but this is what I did it to work for me.