Merge #4433: M2: zero-area fills and clips mark the pixels they touch (view.render-pages)

# Conflicts:
#	vendor/README.md
#	vendor/hayro-interpret/src/interpret/path.rs
This commit is contained in:
bflatastic committed 2026-11-09 18:19:48 +07:00
commit baa131de70
4 files changed
+438 -8

No files matched your search

+1
View File
@@ -23,3 +23,4 @@ mod symbol_mt_builtin_encoding;
mod tiling_cell_placement;
mod type3_text_clip;
mod widgets_above_annotations;
mod zero_area_fill_clip;
@@ -0,0 +1,301 @@
//! Zero-area fills and clips mark the pixels they touch (ISO 32000-2 §10.7.4: "A zero-width or
//! zero-height rectangle paints a line 1 pixel wide", and "the clipping region consists of the
//! set of pixels that would be included by a fill operation").
//!
//! Which row (or column) a line on a pixel boundary marks is not left open. §10.7.4, "Scan
//! conversion rules", in device space:
//!
//! > Pixel boundaries always fall on integer coordinates in device space. A pixel is a square
//! > region identified by the location of its corner with minimum horizontal and vertical
//! > coordinates. The region is half-open, meaning that it includes its lower but not its upper
//! > boundaries. More precisely, for any point whose real-number coordinates are (x, y), let
//! > i = floor(x) and j = floor(y). The pixel that contains this point is the one identified as
//! > (i, j).
//!
//! > Like pixels, shapes to be painted by filling (8.5.3.3, "Filling") and stroking (8.5.3.2,
//! > "Stroking") operations are also treated as half-open regions that include the boundaries
//! > along their "floor" sides, but not along their "ceiling" sides.
//!
//! > A shape shall be scan-converted by painting any pixel whose half-open square region
//! > intersects the shape, no matter how small the intersection is.
//!
//! So a line at device y = 150 lies in pixel row floor(150) = 150 and not in row 149, whose
//! region stops short of 150; a line from device x = 10 to x = 110 marks columns 10 to 109, as
//! its ceiling end at 110 is not part of it. Off a boundary, a line at y = 149.5 marks row
//! floor(149.5) = 149. The rule is stated in device space, whose y axis here points down the
//! page, so row 150 is the one just below the line as the page is seen.
//!
//! Every page is 200 × 200 pt rendered at scale 1, so user `(x, y)` lands on device
//! `(x, 200 - y)`: a line at user `y = 50` lies on the boundary between device rows 149 and
//! 150, and by the half-open rule marks row 150.
use std::sync::Arc;
use pdfcraft_render::{PageRenderer, RenderConfig, RenderRequest, RequestKind};
const SIZE: u32 = 200;
fn build_pdf(content: &str) -> Vec<u8> {
let objs = [
"<< /Type /Catalog /Pages 2 0 R >>".to_owned(),
"<< /Type /Pages /Kids [3 0 R] /Count 1 >>".to_owned(),
format!("<< /Type /Page /Parent 2 0 R /MediaBox [0 0 {SIZE} {SIZE}] /Contents 4 0 R >>"),
format!("<< /Length {} >>\nstream\n{content}\nendstream", content.len()),
];
let mut out = b"%PDF-1.7\n".to_vec();
let mut offs = Vec::with_capacity(objs.len());
for (i, body) in objs.iter().enumerate() {
offs.push(out.len());
out.extend_from_slice(format!("{} 0 obj\n{body}\nendobj\n", i + 1).as_bytes());
}
let xref = out.len();
let size = objs.len() + 1;
out.extend_from_slice(format!("xref\n0 {size}\n0000000000 65535 f \n").as_bytes());
for off in offs {
out.extend_from_slice(format!("{off:010} 00000 n \n").as_bytes());
}
out.extend_from_slice(format!("trailer\n<< /Size {size} /Root 1 0 R >>\nstartxref\n{xref}\n%%EOF\n").as_bytes());
out
}
/// The page drawn by `content`, as RGBA rows of `SIZE` pixels.
fn render(content: &str) -> Vec<u8> {
let pdf = Arc::new(build_pdf(content));
let mut renderer = PageRenderer::new(pdf, RenderConfig::default());
let page = renderer.render(RenderRequest { page: 0, kind: RequestKind::Pixels, tile: None, scale: 1.0, tag: 0, preview: false });
assert!(page.error.is_none(), "render error: {:?}", page.error);
assert_eq!((page.width, page.height), (SIZE, SIZE));
page.rgba.to_vec()
}
fn px(rgba: &[u8], x: u32, y: u32) -> [u8; 3] {
let i = ((y * SIZE + x) * 4) as usize;
[rgba[i], rgba[i + 1], rgba[i + 2]]
}
fn is_red(p: [u8; 3]) -> bool {
p[0] > 240 && p[1] < 15 && p[2] < 15
}
fn is_white(p: [u8; 3]) -> bool {
p.iter().all(|&c| c > 250)
}
/// The red pixels of the page, as `(x, y)`.
fn red_pixels(rgba: &[u8]) -> Vec<(u32, u32)> {
let mut red = Vec::new();
for y in 0..SIZE {
for x in 0..SIZE {
if is_red(px(rgba, x, y)) {
red.push((x, y));
}
}
}
red
}
/// The pixels that are neither white nor full red: partly covered ones.
fn tinted_pixels(rgba: &[u8]) -> usize {
let mut n = 0;
for y in 0..SIZE {
for x in 0..SIZE {
let p = px(rgba, x, y);
if !is_red(p) && !is_white(p) {
n += 1;
}
}
}
n
}
/// Asserts the page is exactly a full-red run of device pixels `x0..x1` × `y0..y1` on white.
fn assert_only_red_run(rgba: &[u8], (x0, x1): (u32, u32), (y0, y1): (u32, u32), what: &str) {
let mut expected = Vec::new();
for y in y0..y1 {
for x in x0..x1 {
expected.push((x, y));
}
}
assert_eq!(red_pixels(rgba), expected, "{what}: the red pixels");
assert_eq!(tinted_pixels(rgba), 0, "{what}: partly covered pixels");
}
const FLOOD: &str = "1 0 0 rg 0 0 200 200 re f";
/// A fill that covers the whole page under any of the CTMs below.
const BIG_FLOOD: &str = "1 0 0 rg -400 -400 800 800 re f";
#[test]
fn zero_height_clip_shows_the_fill_as_one_device_row() {
// User y = 50 is device y = 150, a pixel boundary: row 150 and nothing else.
let rgba = render(&format!("q 10 50 100 0 re W n {FLOOD} Q"));
assert_only_red_run(&rgba, (10, 110), (150, 151), "clip on a pixel boundary");
// Off the boundary (device y = 149.5) the line marks the row it runs through.
let rgba = render(&format!("q 10 50.5 100 0 re W n {FLOOD} Q"));
assert_only_red_run(&rgba, (10, 110), (149, 150), "clip inside a row");
// Inside a translated CTM, as the line is usually drawn.
let rgba = render(&format!("q 1 0 0 1 20 30 cm 10 10 100 0 re W n {FLOOD} Q"));
assert_only_red_run(&rgba, (30, 130), (160, 161), "clip under a translation");
}
#[test]
fn zero_width_clip_shows_the_fill_as_one_device_column() {
let rgba = render(&format!("q 50 10 0 100 re W n {FLOOD} Q"));
assert_only_red_run(&rgba, (50, 51), (90, 190), "zero-width clip");
}
#[test]
fn zero_height_and_zero_width_fills_paint_one_pixel_lines() {
let rgba = render("1 0 0 rg 10 50 100 0 re f");
assert_only_red_run(&rgba, (10, 110), (150, 151), "zero-height fill");
let rgba = render("1 0 0 rg 50 10 0 100 re f");
assert_only_red_run(&rgba, (50, 51), (90, 190), "zero-width fill");
// The same line drawn as a fill and seen through a clip marks the same pixels.
let fill = render("1 0 0 rg 10 50.5 100 0 re f");
let clip = render(&format!("q 10 50.5 100 0 re W n {FLOOD} Q"));
assert_eq!(red_pixels(&fill), red_pixels(&clip));
}
/// Each of the four cases (zero-height and zero-width, fill and clip) on a pixel boundary and
/// off one, by the half-open rule quoted above: a line on a boundary marks the row or column on
/// its floor side, one off it marks the row or column it runs through, and its ends mark every
/// pixel they reach into but not one they only meet at the ceiling side.
#[test]
fn zero_height_and_zero_width_fills_and_clips_on_and_off_a_pixel_boundary() {
let cases = [
// (the line, its device columns, its device rows, what)
("10 50 100 0 re", (10, 110), (150, 151), "zero-height on a boundary"),
("10 50.5 100 0 re", (10, 110), (149, 150), "zero-height off a boundary"),
("10.5 50.5 99 0 re", (10, 110), (149, 150), "zero-height, ends inside pixels"),
("50 10 0 100 re", (50, 51), (90, 190), "zero-width on a boundary"),
("50.5 10 0 100 re", (50, 51), (90, 190), "zero-width off a boundary"),
("50.5 10.5 0 99 re", (50, 51), (90, 190), "zero-width, ends inside pixels"),
];
for (line, columns, rows, what) in cases {
let fill = render(&format!("1 0 0 rg {line} f"));
assert_only_red_run(&fill, columns, rows, &format!("{what}: fill"));
let clip = render(&format!("q {line} W n {FLOOD} Q"));
assert_only_red_run(&clip, columns, rows, &format!("{what}: clip"));
}
}
#[test]
fn a_quarter_turn_maps_a_zero_height_clip_to_one_device_column() {
// `0 1 -1 0 100 20 cm` turns user x into device -y: the line runs up column 100.
let rgba = render(&format!("q 0 1 -1 0 100 20 cm 10 0 100 0 re W n {BIG_FLOOD} Q"));
assert_only_red_run(&rgba, (100, 101), (70, 170), "quarter-turned clip");
}
#[test]
fn a_rotated_zero_height_clip_and_fill_show_a_one_pixel_band() {
// 45 degrees: the line runs diagonally, so it shows as a band about one pixel wide.
let clip = render(&format!("q 0.70710678 0.70710678 -0.70710678 0.70710678 50 50 cm 0 0 100 0 re W n {BIG_FLOOD} Q"));
let fill = render("q 0.70710678 0.70710678 -0.70710678 0.70710678 50 50 cm 1 0 0 rg 0 0 100 0 re f Q");
for (rgba, what) in [(&clip, "clip"), (&fill, "fill")] {
// Along the diagonal from device (50, 150) to (120.7, 79.3), the pixel the line crosses
// corner to corner in each column is mostly red, and the pixels well off it are white.
for step in 5..65 {
let (x, y) = (50 + step, 149 - step);
let p = px(rgba, x, y);
assert!(p[0] > 240 && p[1] < 160, "{what}: pixel ({x}, {y}) on the line is {p:?}");
assert!(is_white(px(rgba, x + 3, y)), "{what}: pixel off the line");
assert!(is_white(px(rgba, x - 3, y)), "{what}: pixel off the line");
}
// The band is one pixel wide: its ink adds up to its length, 100 pixels.
let ink: f64 = rgba.as_chunks::<4>().0.iter().map(|p| 1.0 - f64::from(p[1]) / 255.0).sum();
assert!((90.0..=110.0).contains(&ink), "{what}: ink {ink}");
}
}
#[test]
fn a_thin_rectangle_with_area_keeps_its_partial_coverage() {
// 0.3 pt high is not degenerate: it covers 30 % of device row 149 and is antialiased as
// before, not widened to a whole pixel.
let rgba = render("1 0 0 rg 10 50.2 100 0.3 re f");
assert!(red_pixels(&rgba).is_empty(), "a 0.3 pt rectangle is not painted solid");
for x in 10..110 {
let p = px(&rgba, x, 149);
assert!(p[0] > 240, "row 149 at {x}: {p:?}");
assert!((150..=210).contains(&p[1]), "row 149 at {x} is 30 % covered: {p:?}");
assert!(is_white(px(&rgba, x, 148)) && is_white(px(&rgba, x, 150)));
}
// The same rectangle as a clip keeps the same partial coverage.
let clip = render(&format!("q 10 50.2 100 0.3 re W n {FLOOD} Q"));
assert_eq!(clip, rgba);
}
#[test]
fn a_zero_area_clip_with_nothing_painted_on_it_stays_blank() {
// The fill misses the line the clip keeps.
let rgba = render("q 10 50 100 0 re W n 1 0 0 rg 0 100 200 100 re f Q");
assert!(rgba.as_chunks::<4>().0.iter().all(|p| is_white([p[0], p[1], p[2]])), "page not blank");
// Nothing painted at all.
let rgba = render("q 10 50 100 0 re W n Q");
assert!(rgba.as_chunks::<4>().0.iter().all(|p| is_white([p[0], p[1], p[2]])), "page not blank");
// A clip that is a point keeps nothing, as before.
let rgba = render(&format!("q 10 50 0 0 re W n {FLOOD} Q"));
assert!(red_pixels(&rgba).is_empty() && tinted_pixels(&rgba) == 0, "a point clip shows the fill");
// So does a point a little off zero both ways.
let rgba = render(&format!("q 10 50 0.001 0.001 re W n {FLOOD} Q"));
assert!(red_pixels(&rgba).is_empty() && tinted_pixels(&rgba) == 0, "a tiny clip shows the fill");
}
#[test]
fn the_clip_is_restored_after_q() {
let rgba = render(&format!("q 10 50 100 0 re W n Q {FLOOD}"));
assert_eq!(red_pixels(&rgba).len(), (SIZE * SIZE) as usize);
}
#[test]
fn a_thin_rectangle_scaled_up_to_whole_pixels_keeps_its_area() {
// 1/1024 pt high is under the rasteriser's "nearly zero" threshold, but the rectangle has
// area: scaled 4096 times vertically it covers device y 164..168, four whole rows, and is
// painted as the rectangle it is, not as a line across its bounding box.
let fill = render("q 1 0 0 4096 0 0 cm 1 0 0 rg 10 0.0078125 100 0.0009765625 re f Q");
assert_only_red_run(&fill, (10, 110), (164, 168), "scaled-up thin fill");
let clip = render(&format!("q 1 0 0 4096 0 0 cm 10 0.0078125 100 0.0009765625 re W n {FLOOD} Q"));
assert_only_red_run(&clip, (10, 110), (164, 168), "scaled-up thin clip");
}
#[test]
fn a_slanted_zero_height_line_crossing_a_row_marks_each_row_only_where_it_runs() {
// A slight skew lifts the line from device y 149.52 at x = 10 to 148.74 at x = 110: under a
// pixel high in all, but crossing the boundary between rows 148 and 149 near x = 75. Each
// row is marked where the line runs through it, not along the whole length.
let skew = "1 0.008 0 1 0 0 cm";
let fill = render(&format!("q {skew} 1 0 0 rg 10 50.4 100 0 re f Q"));
let clip = render(&format!("q {skew} 10 50.4 100 0 re W n {FLOOD} Q"));
for (rgba, what) in [(&fill, "fill"), (&clip, "clip")] {
for x in [12, 15, 20] {
assert!(px(rgba, x, 149)[1] < 128, "{what}: ({x}, 149) on the line is {:?}", px(rgba, x, 149));
assert!(px(rgba, x, 148)[1] > 128, "{what}: ({x}, 148) off the line is {:?}", px(rgba, x, 148));
}
for x in [100, 105, 108] {
assert!(px(rgba, x, 148)[1] < 128, "{what}: ({x}, 148) on the line is {:?}", px(rgba, x, 148));
assert!(px(rgba, x, 149)[1] > 128, "{what}: ({x}, 149) off the line is {:?}", px(rgba, x, 149));
}
// One pixel wide: its ink adds up to its length, about 100 pixels, not two rows' worth.
let ink: f64 = rgba.as_chunks::<4>().0.iter().map(|p| 1.0 - f64::from(p[1]) / 255.0).sum();
assert!((90.0..=110.0).contains(&ink), "{what}: ink {ink}");
}
}
#[test]
fn disconnected_subpaths_on_one_line_leave_the_gap_between_them_unpainted() {
// Two zero-height subpaths on user y = 50 (device row 150), x 10..30 and 60..90: the fill
// and the clip mark the pixels each subpath touches, not the gap between them.
let mut expected = Vec::new();
for x in (10..30).chain(60..90) {
expected.push((x, 150));
}
let fill = render("1 0 0 rg 10 50 m 30 50 l 60 50 m 90 50 l f");
let clip = render(&format!("q 10 50 m 30 50 l 60 50 m 90 50 l W n {FLOOD} Q"));
for (rgba, what) in [(&fill, "fill"), (&clip, "clip")] {
assert_eq!(red_pixels(rgba), expected, "{what}: the red pixels");
assert_eq!(tinted_pixels(rgba), 0, "{what}: partly covered pixels");
}
// Overlapping subpaths drawn in opposite directions still paint their union under either rule.
let fill = render("1 0 0 rg 10 50 m 60 50 l 90 50 m 40 50 l f*");
assert_only_red_run(&fill, (10, 90), (150, 151), "overlapping subpaths");
let clip = render(&format!("q 10 50 m 60 50 l 90 50 m 40 50 l W* n {FLOOD} Q"));
assert_only_red_run(&clip, (10, 90), (150, 151), "overlapping subpaths: clip");
}
+1 -1
View File
@@ -39,7 +39,7 @@ Other resource categories retain their existing parent-chain lookup.
| Crate | Version | Licence | Patches | Test |
|---|---|---|---|---|
| hayro-interpret | 0.7.0 | Apache-2.0 OR MIT | (1) select `/AP /N` appearance states via `/AS` (checkboxes, radios, stateful icons) and honour the NoView flag; (2) Type3 Unicode fallback to `/Encoding` glyph names, then printable ASCII; (3) `Type3Glyph::advance_width`; (4) `InterpreterSettings::ocg_overrides` for viewer layer toggles; (5) soft masks whose group lacks `/CS` were dropped (Chrome gradient text); (6) paint nesting cap `MAX_PAINT_NESTING` for tiling patterns and Type 3 glyphs (self-referencing content overflowed the stack); (7) CID width ranges in `/W` and `/W2` clamped to `MAX_CID` (a `0 4294967295 w` range hung); (8) `InterpreterSettings::hide_comments` skips markup annotations but keeps widgets and links (View ▸ Hide all comments); (9) `image_size_ok`: images and masks over 2^28 pixels are not decoded (a fuzzed `/W 4294967295` stencil mask allocated 4 GiB); (10) `MAX_NESTED_PAINTS`: nested paints (forms, Type 3 glyphs and tiling patterns inside one another) share a per-page budget of 50,000 (a glyph showing eight glyphs of its own font, sixteen deep, hung); (11) depends on skrifa 0.47 instead of 0.42 (upstream read-fonts fixed a Type 1 tokenizer that recursed through runs of numbers: a fuzzed font hung or overflowed the stack), with the one API change (`Charset::glyph_id` returns `Option`); (12) annotation appearances whose `/BBox` or `/Matrix` collapses to a line or a point are skipped (mapping them onto `/Rect` divided by zero and handed the device infinite or NaN matrices); (13) a Highlight annotation without a usable normal appearance is drawn from its `/QuadPoints`, `/C` and `/CA` with Multiply blending, as pdfcraft-annot draws highlights (it was not drawn at all); (14) simple-font `/Widths` (`read_widths`): entries only for codes 0–255 (one entry per code below `/FirstChar` was allocated: `4294967295` asked for 34 GB), an entry that isn't a number leaves its code missing instead of ending the array, and a `/LastChar` below `/FirstChar` gives no widths instead of discarding the font for a standard one; (15) the appearance box is mapped onto `/Rect` corner to corner: the translation now accounts for the scale (an appearance whose box didn't start at the origin and differed in size from `/Rect` was drawn shifted); (16) a clip set by `W`/`W*` takes effect after whichever path-painting operator ends the path (`S`, `f`, `B`, … as well as `n`; ISO 32000-2 §8.5.4): it was applied only on `n`, so `re W* S` clipped nothing and the clip stayed pending for a later, unrelated `n`; (17) `InterpreterSettings::cancelled`: once set, interpretation stops before the next content operator (a render pool sets it for every worker when dropped, after an edit or on closing, and for one worker when the watchdog gives up on its render, so renders whose answers nobody can receive stop instead of running to the end); (18) `MAX_PAGE_CONTENT`: the content a page holds at once (its contents, and the forms, tiling patterns and Type 3 glyph procedures being painted) stays within 512 MiB (`decode_content`; once it runs out, `InterpreterWarning::ContentTruncated` is reported (once per page by pdfcraft-render) so a truncated page is not a clean render; each level gives its bytes back when it finishes): forms nest fifty deep and each level kept its content while the next ran, so a form painting itself around a stream inflating to 256 MiB would have held over 12 GB; and Type 0 sampled functions take at most `MAX_SAMPLE_ENTRIES` (2^21) table points and `MAX_SAMPLE_VALUES` (2^23) samples, read no further than `/Size` asks (256 MiB of 1-bit samples asked for over 8 GB); (19) mesh shadings (types 4–7) are sampled only inside the area being drawn (`ShadingPattern::encode_within`, which the vendored hayro renderer calls with that area plus a pixel), within 8 visits per pixel of it plus 4 per triangle (`TriangleSampler`), and patches are triangulated one at a time: points far off the page were sampled over their whole bounding box, up to 65536 × 65536 entries (a fuzzed 147-byte patch stream; a synthetic page passed 6 GB in six seconds), ten thousand overlapping triangles ran for minutes, and every patch became 722 triangles before any limit; meshes hold at most `MAX_MESH_PATCHES` (2^16) patches and `MAX_MESH_TRIANGLES` (2^20) triangles, a lattice needs two to 2^19 vertices per row (`/VerticesPerRow 0` pushed empty rows for ever; one huge row read the whole stream), and a page samples at most `MAX_PAGE_MESH_TRIANGLES` (2^25) mesh triangles in all (a mesh painted a thousand times was triangulated a thousand times); each cut logs a warning; (20) PDF function construction is limited to 64 levels and 10,000 total nodes with cycle detection; calculator parsing and evaluation share procedure depth/work budgets, integer division/bitshift/rotation/index are panic-free, and fixed-size stack errors propagate; (21) a Type 0 font drawn with a substitute that isn't CID-keyed (it isn't embedded, or its program doesn't load) draws `.nLine truncated
| hayro-interpret | 0.7.0 | Apache-2.0 OR MIT | (1) select `/AP /N` appearance states via `/AS` (checkboxes, radios, stateful icons) and honour the NoView flag; (2) Type3 Unicode fallback to `/Encoding` glyph names, then printable ASCII; (3) `Type3Glyph::advance_width`; (4) `InterpreterSettings::ocg_overrides` for viewer layer toggles; (5) soft masks whose group lacks `/CS` were dropped (Chrome gradient text); (6) paint nesting cap `MAX_PAINT_NESTING` for tiling patterns and Type 3 glyphs (self-referencing content overflowed the stack); (7) CID width ranges in `/W` and `/W2` clamped to `MAX_CID` (a `0 4294967295 w` range hung); (8) `InterpreterSettings::hide_comments` skips markup annotations but keeps widgets and links (View ▸ Hide all comments); (9) `image_size_ok`: images and masks over 2^28 pixels are not decoded (a fuzzed `/W 4294967295` stencil mask allocated 4 GiB); (10) `MAX_NESTED_PAINTS`: nested paints (forms, Type 3 glyphs and tiling patterns inside one another) share a per-page budget of 50,000 (a glyph showing eight glyphs of its own font, sixteen deep, hung); (11) depends on skrifa 0.47 instead of 0.42 (upstream read-fonts fixed a Type 1 tokenizer that recursed through runs of numbers: a fuzzed font hung or overflowed the stack), with the one API change (`Charset::glyph_id` returns `Option`); (12) annotation appearances whose `/BBox` or `/Matrix` collapses to a line or a point are skipped (mapping them onto `/Rect` divided by zero and handed the device infinite or NaN matrices); (13) a Highlight annotation without a usable normal appearance is drawn from its `/QuadPoints`, `/C` and `/CA` with Multiply blending, as pdfcraft-annot draws highlights (it was not drawn at all); (14) simple-font `/Widths` (`read_widths`): entries only for codes 0–255 (one entry per code below `/FirstChar` was allocated: `4294967295` asked for 34 GB), an entry that isn't a number leaves its code missing instead of ending the array, and a `/LastChar` below `/FirstChar` gives no widths instead of discarding the font for a standard one; (15) the appearance box is mapped onto `/Rect` corner to corner: the translation now accounts for the scale (an appearance whose box didn't start at the origin and differed in size from `/Rect` was drawn shifted); (16) a clip set by `W`/`W*` takes effect after whichever path-painting operator ends the path (`S`, `f`, `B`, … as well as `n`; ISO 32000-2 §8.5.4): it was applied only on `n`, so `re W* S` clipped nothing and the clip stayed pending for a later, unrelated `n`; (17) `InterpreterSettings::cancelled`: once set, interpretation stops before the next content operator (a render pool sets it for every worker when dropped, after an edit or on closing, and for one worker when the watchdog gives up on its render, so renders whose answers nobody can receive stop instead of running to the end); (18) `MAX_PAGE_CONTENT`: the content a page holds at once (its contents, and the forms, tiling patterns and Type 3 glyph procedures being painted) stays within 512 MiB (`decode_content`; once it runs out, `InterpreterWarning::ContentTruncated` is reported (once per page by pdfcraft-render) so a truncated page is not a clean render; each level gives its bytes back when it finishes): forms nest fifty deep and each level kept its content while the next ran, so a form painting itself around a stream inflating to 256 MiB would have held over 12 GB; and Type 0 sampled functions take at most `MAX_SAMPLE_ENTRIES` (2^21) table points and `MAX_SAMPLE_VALUES` (2^23) samples, read no further than `/Size` asks (256 MiB of 1-bit samples asked for over 8 GB); (19) mesh shadings (types 4–7) are sampled only inside the area being drawn (`ShadingPattern::encode_within`, which the vendored hayro renderer calls with that area plus a pixel), within 8 visits per pixel of it plus 4 per triangle (`TriangleSampler`), and patches are triangulated one at a time: points far off the page were sampled over their whole bounding box, up to 65536 × 65536 entries (a fuzzed 147-byte patch stream; a synthetic page passed 6 GB in six seconds), ten thousand overlapping triangles ran for minutes, and every patch became 722 triangles before any limit; meshes hold at most `MAX_MESH_PATCHES` (2^16) patches and `MAX_MESH_TRIANGLES` (2^20) triangles, a lattice needs two to 2^19 vertices per row (`/VerticesPerRow 0` pushed empty rows for ever; one huge row read the whole stream), and a page samples at most `MAX_PAGE_MESH_TRIANGLES` (2^25) mesh triangles in all (a mesh painted a thousand times was triangulated a thousand times); each cut logs a warning; (20) PDF function construction is limited to 64 levels and 10,000 total nodes with cycle detection; calculator parsing and evaluation share procedure depth/work budgets, integer division/bitshift/rotation/index are panic-free, and fixed-size stack errors propagate; (21) a Type 0 font drawn with a substitute that isn't CID-keyed (it isn't embedded, or its program doesn't load) draws `.nLine truncated
| hayro | 0.7.1 | Apache-2.0 OR MIT | (1) `RenderSettings::{x_offset, y_offset}` to render one tile of a large page; (2) images over `MAX_IMAGE_PIXELS` (2^28) are skipped (a fuzzed `/W 4294967295` hung in resampling); (3) `tiling_cell_scale` keeps a tiling pattern's cell pixmap within 3000 px a side whatever its `/XStep`/`/YStep` (a fuzzed step far beyond `/BBox` allocated 2 GB); (4) stroke widths clamped to 4 × (canvas width + height) device pixels (a fuzzed `/LW 9223372036854775807` allocated 10 GB in stroke expansion); (5) `usable_dash_pattern`: a stroke whose dash pattern could cut it into more than `MAX_DASHES_PER_STROKE` (250,000) pieces, counting kurbo's restart of the pattern at every subpath and `ClosePath`, is drawn solid (a fuzzed `/D [[11] 0]` on a line from x = 92234775807 allocated over 5 GB, `[0.000001] 0 d` on a 20 pt line over 10 GB); (6) a dash pattern with a negative or non-finite entry, or a period that isn't positive, is drawn solid (`[-1 -1] 0 d` looped for ever in kurbo); (7) `render_size` and `render_into`: render into a buffer the caller allocates (PdfCraft renders into pixel-aligned memory that the GUI takes over as texture data); `render` is `render_into` on a new pixmap; (8) checked image source/target/RGBA, alpha-premultiplication scratch and intermediate sizes before resampling, finite transforms and exact source/mask buffers; sources wider than u16 may shrink before backend limits, with a 2^20 source-axis cap and conservative 128 MiB filter-planning estimate; an over-limit or failed resize keeps the original image resolution and geometry when the source fits the backend, otherwise skips it, with a logged warning; staging, resampling output/scratch, RGBA conversion and padding buffers use fallible reserves; (9) `may_paint_canvas`: a fill or stroke whose control-point box, grown by how far its paint reaches past the path (half the stroke width times the larger of the miter limit and √2) plus 0.5 user units and 2 pixels, misses the canvas is not drawn, so a tile no longer strokes and fills every path of its page (item 5 of #623); `set_skip_offscreen_paths` turns this off for the regression test; (10) `/Interpolate` governs the pre-resize too (#624): a minified image that does not request interpolation is pre-resized with nearest-neighbour (since (21), only inside Type 3 glyphs), planned without the Catmull-Rom filter limits (`image_resampling_size` takes the flag); a Type 3 glyph image is sampled bicubically only when interpolated; a minified image with a matching soft mask is nearest-sampled straight into premultiplied RGBA; (11) `may_paint_rect`: an image whose stream-size box, mapped to the device, misses the canvas is skipped before decoding (decoded data can only shrink against that box), so a tile of an image-heavy page no longer decodes, resamples and rasterizes every image on it; (12) preview renders (`InterpreterSettings::preview`: backdrops, thumbnails, grid cells, signature-drag backgrounds) skip images under `PREVIEW_MIN_IMAGE_AREA` device pixels, while final renders always draw them; (13) reading colours (#897): `RenderSettings::color_replacement` takes a `ColorReplacement` (text colour, background, `only_black`, `line_art`) that remaps solid text and line-art paint while rendering, glyph outlines counting as text and stencil-mask ink as line art; images, image alpha masks, soft masks and pattern cells keep their colours; `render_pdf` gains a `color_replacement: Option<ColorReplacement>` argument (pass `None` for true colours); the upstream-only `[dev-dependencies.log]` entry is removed from `Cargo.toml` (log is a normal dependency since the logging patch), so `cargo test -p hayro` runs this crate's unit tests; (14) a shrunk image that is interpolated (or, since (21), area-averaged) and whose axes lie along the device's (upright, mirrored or a quarter turn, as on a page under `/Rotate`) is snapped to whole device pixels: shrunk once to its rounded device rectangle (halves round up, so a tile snaps an edge where the whole page does) and drawn 1:1 from the rounded corner, instead of a ceil-sized raster resampled again at a fractional scale and offset (`snap_minified_image`; scans looked soft next to Acrobat, and until #5530 a turned one still did, up to 200 grey levels off the same page drawn upright). An image counts as axis-aligned when the terms the snap drops move its far edges by at most a hundredth of a device pixel (`SNAP_SKEW`), not by a tolerance on the coefficients, which let a slight skew of a very wide image through; and the snapped 1:1 transform is used only when the shrink produced the snapped size, so a failed resize keeps the full transform instead of drawing the source raster at its source size; (15) a soft mask of another size than its image is filtered when shrunk, whatever its `/Interpolate` (#1649): such a mask carries the shape on its own (Word saves text as a tiny black image with a glyph-bitmap mask), and nearest-neighbour dropped every stroLine truncated
| hayro-jbig2 | 0.3.0 | Apache-2.0 OR MIT | (1) at most 2^28 pixels per bitmap and page bitmap, and 2^25 cells per halftone grid and grayscale image (each side could be 65535: 4.3 billion pixels decoded one by one, and a 4-byte value per cell); (2) at most 2^26 symbol pixels per symbol dictionary (a fuzzed dictionary decoded for minutes); (3) a symbol dictionary's height classes are capped at one per new symbol and its export runs at `2 × symbols + 1`, each plus `EXTRA_EMPTY_STEPS` (1024): an empty height class or a zero-length export run doesn't advance, and past the end of its data the arithmetic decoder can decode them for ever (one changed byte hung the renderer); (4) a segment header's long-form referred-to segment count is capped at `u16::MAX` and a larger count is refused before its retention or referred-to bytes are read: the 29-bit count went straight to `Vec::with_capacity`, a reservation of about 2 GiB whose failure aborts the process (from storytold/craft-libs#176); (5) what a page's segments hold for later ones (intermediate regions, pattern and symbol dictionaries with their headers and retained contexts, and Huffman tables) is at most 64 MiB, two square bitmaps of 16,384 a side (`MAX_RETAINED_WORDS`), and a dictionary's new and exported symbols are counted against it as they are made: each was bounded on its own, but a few dozen bytes an intermediate region held 33 MB each, and 8 MiB symbols exported again and again killed the process, so a few kilobytes could exhaust memory; (6) a segment may refer to at most 2^20 symbols, checked before any are collected: references may repeat, and 65,535 of them to one dictionary, in a 78 KB stream, asked for 17 GB; (7) a pattern dictionary keeps at most 16 MiB of shifted copies, which only speed up drawing, and none that wouldn't fit what the page has left (`MAX_SHIFTED_WORDS`); (8) a custom Huffman table has at most 2^16 lines, and a stream with its globals at most 2^20 segments and 2^22 references, checked as they are read: both grew before anything counted them, and PDFs of a kilobyte or so reached 5 GB and more behind nested Flate; (9) a page past the bounds of (1) is refused when the stream is opened: a caller sizes its output from the header before the page bitmap is made, and an Indexed image in a 743-byte PDF asked for 137 GB, which aborts; (10) a stream may ask for at most 2^30 units of decoding work, four of the largest pages, about 6 s to 17 s (`MAX_WORK`): decoding a bitmap costs a pixel each and 4 a row, copying one a word each and 1 a row, and each integer an item reads costs 38, what one takes at worst, so one with no pixels pays too, before it is decoded: each bitmap was bounded, but nothing bounded how many there were, and a 795-byte PDF took 265 s; (11) `Image::decode_within` spends from what a run of images may still do, starting with its page's pixels, and `charge_reading` charges reading a stream and its globals before anything is parsed, so an operation over a document can bound what `MAX_WORK` bounds for one image, and images that fail or decode nothing add up too: a file of thousands of images made to reach that limit took as many times as long; (12) adding to a location, a reference offset, a symbol's corner or a Huffman range line near the end of an `i32`, and negating a decoded integer of 2^31, overflowed: a panic wherever overflow is checked. The refinement context, a text region's corners, the integer decoder and the Huffman table wrap, as a release build did, and `Bitmap::combine` saturates, which comes to the same, as a location that overflows is past the end of any page. What is drawn doesn't change; (13) a bitmap filled with a default pixel of 1 (a page, or an intermediate text or halftone region) had 1s past its width in the last word of each row, and a refinement, which reads its reference a word at a time, read them as pixels where the standard has 0 (6.3.5.2): refining such a reference not a multiple of 32 wide decoded to other pixels than were coded, release builds too. `Bitmap::clear_padding` clears those bits when a bitmap is filled with 1s, as cutting symbols and patterns from a collective bitmap already did. Ghostscript reads the test's page and text streams as they decode now; (14) a region's location is unsigned (5.4.4), so one past `i32::MAX` is off the page, where the decoder took it for a signed one: a region there was drawn back onto the page from the left or the top (at 0xFFFFFFFC, four pixels left of it), and a refinement there, of the page or of a region at the same place (7.4.7.5), was refused as an overflow, and the page with it. `Bitmap::combine_region` keeps such a location past the page. A refinement of another region refines it where it is, as Table 35 has it (GRREFERENCEDX and GRREFERENCEDY 0), whatever the two locations say; a refinement of the page, see (16); (15) a refinement whose reference is offset right of it (GRREFERENCEDX above 0, which a refined text instance has from a wider bitmap, TaLine truncated
| lopdf | 0.45.0 | MIT | (1) PNG predictor rows longer than the data are refused before their buffers are allocated (a fuzzed `/Columns 4294967295` allocated two 4 GiB rows), and empty frames return without row buffers; (2) predictor row widths use saturating arithmetic or reject overflow; (3) sub-byte TIFF Predictor 2 scratch is bounded by the samples present in the input instead of the declared `/Colors`, aligned with [lopdf#589](https://github.com/J-F-Liu/lopdf/pull/589); (4) the object lookup keeps its cycle history through compressed objects, requires an ordinary in-file container, and caps the chain of indirect lookups at 16 (a chain of new objects, each a `/Length` compressed in a container whose own `/Length` names the next, or a stream whose `/Length` names the next stream, overflowed the stack: a dev build's 2 MiB thread within 800 hops); (5) object-stream members are parsed within their own extent (up to the next distinct offset), an entry whose offset repeats an earlier entry's is skipped (so a repeated object number can resolve to its earlier entry), and offsets are processed in index order; (6) `find_latest_trailer`: a rebuild takes a `/Type /XRef` stream dictionary as the trailer when the file has no `trailer` keyword (the latest in the file wins, as a later `trailer` would), so a concatenated or truncated file keeps its /Info and /ID instead of failing to load; a candidate whose /Root is the catalog beats one whose /Root is another dictionary, and an in-file /Root must match its generation (#2365) | (1) `inspect::tests::png_predictor_rows_longer_than_the_data_are_refused_before_allocating`, `inspect::tests::empty_png_predictor_frames_do_not_allocate_rows`; (2) `inspect::tests::tiff_subbyte_predictor_row_width_overflow_is_refused`; (3) `inspect::tests::tiff_subbyte_predictor_scratch_is_bounded_by_available_samples`, `inspect::tests::tiff_subbyte_predictors_keep_components_rows_and_padding`; (4) `inspect::tests::compressed_object_self_container_does_not_recurse`, `inspect::tests::compressed_object_mutual_containers_do_not_recurse`, `inspect::tests::object_stream_length_cycle_does_not_recurse`, `inspect::tests::compressed_object_container_chain_does_not_recurse`, `inspect::tests::compressed_length_chain_does_not_recurse`, `inspect::tests::plain_stream_length_chain_does_not_recurse`, `inspect::tests::compressed_objects_and_indirect_stream_length_still_load`, `inspect::tests::compressed_length_in_a_container_with_an_indirect_length_still_loads`; (5) `inspect::tests::object_stream_member_extents_bound_owned_strings`, `inspect::tests::object_stream_member_extents_preserve_index_order_and_whitespace`; (6) `inspect::tests::rebuilt_file_keeps_the_info_of_its_cross_reference_stream`, `inspect::tests::rebuilt_file_prefers_a_trailer_whose_root_is_the_catalog` |
+135 -7
View File
@@ -3,7 +3,7 @@ use crate::context::{Context, path_as_rect};
use crate::device::Device;
use crate::util::{BezPathExt, Float32Ext};
use crate::{BlendMode, FillRule, Paint, PathDrawMode, StrokeProps};
use kurbo::{BezPath, Cap, Join, PathEl, Point};
use kurbo::{Affine, BezPath, Cap, Join, PathEl, Point, Rect, Vec2};
use smallvec::smallvec;
use std::borrow::Cow;
@@ -93,11 +93,127 @@ pub(crate) fn apply_pending_clip<'a>(context: &mut Context<'a>, device: &mut imp
if let Some(rule) = context.clip_mut().take()
&& !context.path().elements().is_empty()
{
let clip_path = context.get().ctm * context.path().clone();
context.push_clip_path(clip_path, rule, device);
let ctm = context.get().ctm;
// PdfCraft patch (65): a clip that encloses no area keeps the pixels a fill of it marks
// (see `degenerate_fill_area`), as ISO 32000-2 §10.7.4 says of clipping: "the clipping
// region consists of the set of pixels that would be included by a fill operation".
match degenerate_fill_area(context.path(), ctm) {
Some(area) => context.push_clip_path(area, FillRule::NonZero, device),
None => {
let clip_path = ctm * context.path().clone();
context.push_clip_path(clip_path, rule, device);
}
}
}
}
/// PdfCraft patch (65): the device-space area a fill marks for a path whose bounding box (user
/// space) has exactly no width or exactly no height, but not both, under `ctm`: one area per
/// subpath (see `degenerate_line_area`), kept as separate subpaths of one path, so a gap between
/// two subpaths on the same line stays unpainted (ISO 32000-2 §10.7.4 marks only the pixels the
/// shape touches). Every area winds the same way, so the non-zero rule paints their union. `None`
/// for a path with area, a path that is a point, or one none of whose subpaths is a line: those
/// paint as before.
pub(crate) fn degenerate_fill_area(path: &BezPath, ctm: Affine) -> Option<BezPath> {
let bbox = path.fast_bounding_box();
if (bbox.width() == 0.0) == (bbox.height() == 0.0) {
return None;
}
let mut area = BezPath::new();
let mut add = |subpath: &BezPath| {
if subpath.elements().is_empty() {
return;
}
let Some(mut corners) = degenerate_line_area(subpath.fast_bounding_box(), ctm) else {
return;
};
// Shoelace: wind every area the same way, so overlapping ones add up under non-zero.
let twice_area: f64 = (0..4)
.map(|i| {
let (p, q) = (corners[i], corners[(i + 1) % 4]);
p.x * q.y - q.x * p.y
})
.sum();
if twice_area < 0.0 {
corners.reverse();
}
area.move_to(corners[0]);
for corner in &corners[1..] {
area.line_to(*corner);
}
area.close_path();
};
let mut subpath = BezPath::new();
for el in path.elements() {
if matches!(el, PathEl::MoveTo(_)) {
add(&subpath);
subpath.truncate(0);
}
subpath.push(*el);
}
add(&subpath);
(!area.elements().is_empty()).then_some(area)
}
/// PdfCraft patch (65): the corners of the device-space area a fill marks for one subpath whose
/// bounding box `bbox` (user space) has exactly no width or exactly no height, but not both,
/// under `ctm`. ISO 32000-2 §10.7.4 paints "any pixel whose half-open square region intersects
/// the shape, no matter how small the intersection is", and its example says "A zero-width or
/// zero-height rectangle paints a line 1 pixel wide". Such a path encloses no area, so the
/// rasteriser marks nothing: the fill used to fall back to a thinnest-line stroke along the box
/// (half-covering two rows when the line fell on a pixel boundary), and a clip of it hid
/// everything painted after it. A box with area, however thin, is not one of these: scaled up it
/// can cover many pixels.
///
/// When the line stays within one device row or column (counting a line less than 1/256 of a
/// pixel across as lying exactly along the axis, at its middle), the area is the run of whole
/// pixels it touches, by the half-open rule: from the floor of its low end to the ceiling of its
/// high end, at least one pixel. Otherwise (a rotated or skewed `ctm` that carries it across
/// rows and columns) it is a band one device pixel wide centred on the line, like the thinnest
/// line of §8.4.3.2, so each row or column is marked only where the line runs through it. `None`
/// for a box with area, a point (both sides zero), a non-finite box, or a `ctm` that collapses
/// the line to a point.
fn degenerate_line_area(bbox: Rect, ctm: Affine) -> Option<[Point; 4]> {
let flat_x = bbox.width() == 0.0;
let flat_y = bbox.height() == 0.0;
if flat_x == flat_y {
return None;
}
let a = ctm * Point::new(bbox.x0, bbox.y0);
let b = ctm * Point::new(bbox.x1, bbox.y1);
if ![a.x, a.y, b.x, b.y].iter().all(|v| v.is_finite()) {
return None;
}
let along = b - a;
let length = along.hypot();
if !length.is_finite() || length <= 0.0 {
return None;
}
let device = Rect::from_points(a, b);
let (x0, x1) = touched_pixels(device.x0, device.x1);
let (y0, y1) = touched_pixels(device.y0, device.y1);
if x1 - x0 <= 1.0 || y1 - y0 <= 1.0 {
return Some([Point::new(x0, y0), Point::new(x1, y0), Point::new(x1, y1), Point::new(x0, y1)]);
}
let half = Vec2::new(-along.y, along.x) * (0.5 / length);
Some([a + half, b + half, b - half, a - half])
}
/// PdfCraft patch (65): the device pixel boundaries `(first, end)` of the pixels a span `lo..=hi`
/// (`lo <= hi`, finite) touches along one axis by the half-open rule, at least one pixel. A span
/// under 1/256 of a pixel is taken at its middle, so a line along a device axis that a CTM's
/// rounding tilts slightly still marks one row or column.
fn touched_pixels(lo: f64, hi: f64) -> (f64, f64) {
let (lo, hi) = if ((hi - lo) as f32).is_nearly_zero() {
let mid = lo + (hi - lo) / 2.0;
(mid, mid)
} else {
(lo, hi)
};
let first = lo.floor();
(first, hi.ceil().max(first + 1.0))
}
pub(crate) fn close_path(context: &mut Context<'_>) {
// This is necessary to prevent artifacts (see for example issue 157),
// but it does cause some weird lines (maybe conflation artifacts) in
@@ -151,10 +267,22 @@ pub(crate) fn fill_path_impl<'a>(
// pdf.js issue 4260: Replace zero-sized paths with a small stroke instead.
let bbox = path.fast_bounding_box();
match (
(bbox.width() as f32).is_nearly_zero(),
(bbox.height() as f32).is_nearly_zero(),
) {
// PdfCraft patch (65): see `degenerate_fill_area`. Painted with the non-zero rule: the
// area is one simple shape, whatever rule the path was filled with.
if let Some(area) = degenerate_fill_area(path, base_transform) {
let draw_mode = PathDrawMode::Fill(FillRule::NonZero);
if let Some(rect) = path_as_rect(&area) {
device.draw_rect(&rect, Affine::IDENTITY, &paint, &draw_mode);
} else {
device.draw_path(&area, Affine::IDENTITY, &paint, &draw_mode);
}
return;
}
// PdfCraft patch (65): only a box with exactly no width or height (by now a point) is
// stroked. A box with area, however thin, is filled as the shape it is: a "nearly zero"
// side scaled up by the CTM can cover many device pixels.
match (bbox.width() == 0.0, bbox.height() == 0.0) {
(false, false) => {
let draw_mode = PathDrawMode::Fill(fill_rule);
if let Some(rect) = path_as_rect(path) {