I think that I have the same or at least a related problem: When printing djvu files to my Samsung ML-2010R using the SPLIX driver, I repeatedly got session timeouts and and a very high CPU utilization due to pdftoraster-poppler. Replacing /usr/lib/cups/filter/pdftoraster-poppler by a symlink to /usr/lib/cups/filter/pdftoraster solves the problem. The printer is fed as fast as possible and the CPU utilization does not skyrocket.
Could it be that the SPLIX driver triggers a bug in the poppler code? (Maybe this interesting: The problem goes away as well by using the foomatic/GDI driver instead of the SPLIX driver. But in my opinion the foomatic/GDI driver lacks features and printout quality is lower.)
I think that I have the same or at least a related problem: When printing djvu files to my Samsung ML-2010R using the SPLIX driver, I repeatedly got session timeouts and and a very high CPU utilization due to pdftoraster- poppler. Replacing /usr/lib/ cups/filter/ pdftoraster- poppler by a symlink to /usr/lib/ cups/filter/ pdftoraster solves the problem. The printer is fed as fast as possible and the CPU utilization does not skyrocket.
Could it be that the SPLIX driver triggers a bug in the poppler code? (Maybe this interesting: The problem goes away as well by using the foomatic/GDI driver instead of the SPLIX driver. But in my opinion the foomatic/GDI driver lacks features and printout quality is lower.)