Comment 5 for bug 450898

With trunk r13454, the offending file opens fine using the Poppler method. If using our standard one, it just hangs here and doesn't seem to take up a ton of ram or end up crashing. In gdb I got tired of waiting and ended up hitting Ctrl+C which threw a segfault related to libcroco and text... given the difference in text handling between poppler and the regular open method it seems worthwhile to at least attach the backtrace for the heck of it.