meh.

@cxhartmann the problem is the Ruby side of things expect `process_page` to store its value in a `STRING*`, which is not the case anymore. With that change it's going to...

@cxhartmann yes, and the biggest problem is getting this gem to work with both pre and post 3.04.

Haven't had the time to work on it unfortunately, it's on my endless TODO list :rage4:

I'll have a look very soon (likely toward the end of the weekend).

I'm very sorry I haven't looked into this yet, I've been very busy but I promise I will as soon as I have time.

I think this is an OS X specific issue, and I don't have such a machine to fix this problem.

@juniorjp1989 oh, that's almost good to know then, guess it's a problem with non Arch Linux systems.

It needs GCC and to compile stuff, I think you can't do that on Heroku.

Now that I think of it, it could be an issue with writing to `/tmp`. Do you know where you can write temporary files on Heroku?

It looks like the process has been killed by a supervisor, it could have used too much processor or something like that, you should contact Heroku and ask for clarification.