@trejrco @mrcorkster the devices should be IPv6-aware and avoid the rush later (assuming the net’s infrastructure ever moves forward)

@mrscorkster What they would say about our (three adults, one two-year old, and two-month old twins) two weeks in a one-bedroom condo?

@mrcorkster of course, IPv6 is seeing almost no traction in the consumer space, where the explosion in connected devices has occurred

@neclimdul using #dompdf 0.5.1? Could be a problem with the _autoload method. Somewhat similar: http://stackoverflow.com/questions/3248199

@jorisw prefer the group if that’s ok. I’m still not sure what the cause is and if this is a new bug.

@jorisw That does seem to be a loop, but I’m not sure what’s going on. Shall we take the discussion to the support forum to hash it out?

@jorisw Could you try the latest dev code, either via SVN or download a nightly at http://eclecticgeek.com/dompdf/

@jorisw Seems unlikely that a loop would be encountered with such a simple doc. What’s your memory limit? PHP version?

@jorisw I was able to render with 0.5.1, 0.6.0 beta 1, and the latest development code. What kind of errors do you get?

@jorisw I’m not seeing the same issues with DOMPDF, your sample table rendered fine.