Vlákno názorů k článku Chromebook a Chrome OS na vlastní kůži od Pavel Tišnovský - Ahoj, prvni veci, co muzes vyzkouset, je prohnat...

Ahoj, prvni veci, co muzes vyzkouset, je prohnat ty PNG soubory pngcrushem, ktery napriklad dokaze vyhodit spatny bloky atd. (muzou to byt nejaka metadata pro NSA ;-). Popr. jestli bys je mohl nekde zverejnit, rad se na to podivam.

Takze ty PNG obrazky - vypadaji korektne, spousta softwaru s nimi nema problemy (MTPaint, Opera atd.). Jedina ponekud zvlastni vlastnost je v tom, ze obsahuji spoustu IDAT bloku a ne jen jeden blok:

pngcrush -n -v Screenshot_2013-09-05_at_19.56.44.png

Opening file Screenshot_2013-09-05_at_19.56.44.png for length measurement
Allocating read structure
Allocating read_info, end_info structures
Reading IHDR chunk, length = 13.
Reading IDAT chunk, length = 8192.
Reading IDAT chunk, length = 8192.
---opakujeme asi 40x ---
Reading IDAT chunk, length = 8192.
Reading IDAT chunk, length = 8192.
Reading IDAT chunk, length = 3910.
Reading IEND chunk, length = 0.
Destroying data structs
Recompressing Screenshot_2013-09-05_at_19.56.44.png
Total length of data found in IDAT chunks = 315206

ENTERING MAIN LOOP OVER 200 METHODS
Allocating read and write structures
Allocating read_info, write_info, end_info structures
Initializing input and output streams
Reading info struct
Transferring info struct
IHDR chunk data:
Width=1366, height=768
Bit depth =8
Color type=2
Interlace =0
Setting IHDR
Found 0 unknown chunks
unknown chunk handling done.

Begin interlace pass 0
Reading and writing end_info data
Destroying data structs

FINISHED MAIN LOOP OVER 200 METHODS

CPU time used = 0.050 seconds (decoding 0.050,
encoding 0.000, other 0.000 seconds)

To neni nic spatneho, spis bych to videl na problem v konkretni PNG ctecce - kde to prosim presne nefungovalo? IE? :-D