Any attempt to print with chromium causes sigsev

[gtodd at iciti.ca]

Hi, I think this is a well known bug? Should I file a PR on 
the port?  

The main chromium development platform seems to be Windows (and
some Linux) where the bug does not manifest. Upstream they'd like
bug reports with backtraces and patches! I am attempting to build
a debug version of trunk to see if this has been resolved and get
a meaningful trace on the crash with our latest version. 

These are non-trivial operations at this site ;-)

Since this seems difficult to patch/fix for FreeBSD should the crash
be mentioned in UPDATING or pkg-message?

Regards,

GRT