Oncle Tom

Nope; try without running any JS to see if it's the parsing/rendering; try another version of the software etc. Or look if there is any bug related to that on their bugtracker — https://code.google.com/p/wkhtmltopdf/issues/list?can=2&q=segmentation+fault

@pro100sanya yup; I've updated to tip with this URL to link the latest static build for each platform: https://code.google.com/p/wkhtmltopdf/downloads/list?can=3&q=static

@pro100sanya yep sure, it's the Static build for OSX or example: https://code.google.com/p/wkhtmltopdf/downloads/detail?name=libwkhtmltox-OSX-0.10.0_rc2.tar.bz2&can=2&q= (avoid the DMG image).

I guess @malladye suggests to alter the title to "129 bytes to enable HTML5 markup and styles on old browsers" — because HTML5 also contains video, audio, user media features and many more.

Which would not work with your trick.

As a side note, you can also add the "main" and "menu". I'm sure some others are missing too.

OSX Users should prefer the static build for production usage, to to VERY VERY large filesize PDF generation. Known bug: http://code.google.com/p/wkhtmltopdf/issues/detail?id=886

Beware jQuery.data also can treat content as integer so if your really need a number higher than a 32 bits integer, it will be truncated.

jQuery.attr('data-blabla') is safer if you need to deal with data integrity.