Yes, it has been significantly changed: we switched from open source CSS Parser Project library to our own CSS parser/cascading engine. Obviously the issue is there.
[language=java:1go4b2xd][2015-11-02 16:46:17,947] java.lang.RuntimeException: stack underflow
at org.zefer.css.y.Ã’00000(Unknown Source)
at org.zefer.css.yb.o00000(Unknown Source)
at org.zefer.css.f.Ã’00000(Unknown Source)
at org.zefer.html.doc.css.c.Ã’0O000(Unknown Source)
at org.zefer.html.doc.PD4MLHtmlParser.buildDocument(Unknown Source)
at org.zefer.pd4ml.PD4ML.o00000(Unknown Source)
at org.zefer.pd4ml.PD4ML.render(Unknown Source)
at org.zefer.pd4ml.PD4ML.render(Unknown Source)
at org.zefer.pd4ml.PD4ML.render(Unknown Source)[/language:1go4b2xd]
Even if the issue not in the new CSS parser, there is a lot of adjustments in the main converter code.
An HTML code sample (incl. its CSS resources) which 100% throws an exception on your site would help a lot to determine a problem reason.
(I am afraid, the blank HTML is not the right sample – the exception is thrown by CSS parsing and the HTML does not refer to any CSS resources)
