I let gpdf go for 20 min CPU on a moderately fast (1 GHz) laptop, and it still didn't display. By the way, I noticed that the process eating all the CPU time is not actually gpdf, but Gnome-pdf-viewer. This process also expands to use about 12 MB of memory (I don't understand how these two interact.) Xpdf displays the document in about 1 second. (It ends up using about 9 MB.
Dave Raymond Filip Van Raemdonck writes: > tags 288346 + help moreinfo unreproducible > thanks > > As for the file David sent to the BTS: it works fine here, just as it does > for Rob and his friend. I'm not sure what might be the problem. > > On Tue, Jan 18, 2005 at 12:21:12AM +0100, Thomas Petazzoni wrote: > > > > Same problem here with my unstable system up-to-date. Attached PDF > > triggers the problem. > > Thomas, about your file: that's a pdf only in file format :) > In reality it's just two big bitmaps, and, admitted, gpdf does need a few > seconds before it is able to display anything. But that's because it is > not very good at displaying big graphics. And it does display the file > eventually, if you just wait a little. > > > Regards, > > Filip > > -- > "If supporters' vociferousness and flamosity are valid measures of an OS' > enterprise readiness, Windows is obviously less enterprise-ready than > Linux: Steve Ballmer alone has shown as much anti-Linux vitriol as all > the pro-Linux, anti-Microsoft zealots put together." > -- Robin Miller -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
