ocsbilisim / dompdf

Automatically exported from code.google.com/p/dompdf
0 stars 0 forks source link

Last page of outputted PDF has strange text #509

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I have this documentation stored in a database, upon retrieval, the code is 
formed into HTML and then uses DOMPDF to create a PDF document for storage and 
transfer between customers. 

Some sample HTML can be found at the following:

http://pastebin.com/JwE9RC5t

The problem is this black bar that appears on the last page of the document. 
Upon closer inspection I found that it is random text reading the following:

1SfDSDPfPSf759098798a89190708150959878298958947870982708497958725968989594907a96
5989080983iawhwohowoiaownana-nrapah-anrarhpa-ne2C2ieCihehsosoh2eCihCb-bn-nbnoana
ntpwfVtVpufufVtwescmpcGhmhpcGpapcpaoPoPoe1.7.7.V.7l.l.r.V.7.V.l.V.r.V.V.r.b.b.5e
rbrpberoceafecereoaocenCcCceCencncecrosesesenlgnlgln4362464351313el2421ul1341342
5a3u2e61l4a15424e12423213ItItItaircr-r-iricri-tbtebililebi0e0grhnTnueuereAreAeur
ururoiTioiTi-cie-cupce-uecpicec-nxueue.n.n.a.t.a.a.t.lPunacaci2nksetenentetv3'cx
sbl1231213bhbckmkmkpkp/tlmsibibryseueupmodfrfrfiefcfecototototsntntnt4aFia/olosu
susfefev0v0vasha.i.i.i.utusieotonN31eoioiobpbphxiofofoenenelPlPlPlflfdte:agVaVax
laxlalxg(alEmrtrt7linaectlhsososou8grtrtrtlbisufakgngngan:oeCtnctfltPlouiuououoi
o0i0i0itoiAtnrnrnsghbearftptaiatisbsb-nxuh:lrlrlubudebebd5rilrcotaefrtC2C2f:eneo
xloxlolocpeo:tsaeobloblobltcAp/p/peateFaeaFeFergrgeac9alp-enunununupBst2tEsefefs
efseisrcetDItaefefelrlolo>apsbtsbsdsdtdbh-hlhlir1tataosos/s/sirlPp:i:ixotrerer-R
do:deysoCaSmSmcltltlt:eoldlAroe1i-3e3irtbhlatitatglrfraosruPnInIhwswm.iosnsnsnst
ulululhfhfopololp0Oscd10dwnsususeibltismsmfrbtscnFdndnan-/rioeoeoiyro0ahofo,o,o1
21stsoNoNelelkegeceyotgclbnuslsmsoaralbtaGnuntntnunt0hPaerlhlbslutyrprprh:bfueom
tiyMucliaialsbso0e0epnryaoxo:menlalalesoe0peIsMldwswsuehnter02nCnC20i,dbk:paocer
)agbnsewncnc2323athegftfidia515hPeaekelasltBiltTernknknladsi-spspspaw/ltetehalap
axp02esl0dtatrgrPn/dlgpepoltlyhsrpepepesNinlomaomofdfdltp0c0r9e9e9ecrcCadim:odlr
ltus:arlrlisduibenynyahlo:au-s-s-adtnsatwtiararcirvr2eseseapelbtbtonupWililstmyd
elafenmosaeiec0101estcedraluezsbhetetasdedndndnAnrp-sh3131rMhuec(FpFptsloe3tbetd
otmyla818mCeodededawdTasals1eisououoTcenirnpdinsftniuiuiuiseones13ieapklnfsfsfif
exeigdoix-odsrchnscriziz0itefalnitrgantlhiensotrawtoanemacu27dreasaohfdgeiepgrd,
lnananaetfivri-uelxnieuetytitdeilNlararonchaesnihfetmntisnlrsrslfinshlgulatnayea
otDlxewldldldletfoeuyptdeahrebcltldnuphrwferiwedaushfetrititefecsreoxsnsnsihnsib
drticionolxlailteiestatyraononehspehufbtiftsmdinbudoeigloxolwaresdstim-erexhshtb
scnsueslbeiauitslteitoanapdemnhestrot(atiGletelupaontnuofsepneboatapislkdxmnhuyr
dplpdrlpihitepeaecieneurdebnaioangcadadreonpgsreulnolenoueneueuvmsreprmxdebdeclP
dPd,psaArfpsaent,t,bopoletibohagenototaerbxipoefeftninorntlrehtaehstototoldhtbnt
bhbhae,aineonpevaeueutntuotmegololoeisnPalstPfkVf-f-osdbt)toeiDiahnenenl-nliflaw
Tesenlsdsclcotofcheauhghgeriowacwhlopdmrlmarcgcgcgmifuepnhcetlsarpealearigoadhrt
dboabienvact,opebnrehntelasnaierleceolencoynynynro,icntgtsetmlcnhonasotrvetoe:tc
nobvoaqephednohefludvberacelorsoatiesntncrhltinesoergtkeametisndtmlplopowbo.ebop
dvrfoaoiuebgbleultadrilhsenelroebieieiedpdtntctnehnerhgfkodetiaxidpuananaintneto
eugcgcgodrnt8rhueiegt5cpehataeaortPeocotioihabnSnbfnlegIlptoaoh(rhtlpwoelt5erobo
.pap9meobldr8a,oeatasob/rkertndefieyltdostlcopehg.ealsearpIaitftpiematfSlrlceiuo
f.flGesobphrl.oesocTstoecpysinklslpieabite,n

I am currently running:

DOMPDF 0.6.0 Beta 3, PHP 5.3, Mac OS 10.7.4

I've attached a screenshot of the black line. 

Original issue reported on code.google.com by chrisand...@gmail.com on 28 Jun 2012 at 5:25

GoogleCodeExporter commented 8 years ago
Something like this is typically caused by a document structural problem that 
dompdf has trouble deciphering. Have you run your HTML through a validator to 
look for any serious problems?

One issue I see on initial glance are block elements contained within inline 
elements. This is known to cause reflow issues (see issue 116). You should 
first attempt to clean up those problems and see if that improves the render.

Original comment by eclecticgeek on 29 Jun 2012 at 2:33

GoogleCodeExporter commented 8 years ago

Original comment by eclecticgeek on 24 May 2013 at 3:00