Closed Bug 960315 Opened 11 years ago Closed 9 years ago

really bad performance on this pdf

Categories

(Firefox :: PDF Viewer, defect, P4)

x86
macOS
defect

Tracking

()

RESOLVED FIXED
Firefox 45

People

(Reporter: fitzgen, Unassigned)

References

Details

(Whiteboard: [pdfjs-c-performance][pdfjs-d-text-selection])

bdahl says that the text layer's algorithm is breaking down and creating a div for every character. http://www.dwarfstd.org/doc/Debugging%20using%20DWARF.pdf It's better with "#textLayer=off" in the url, but still not as good as pdfjs usually is.
Priority: -- → P4
Whiteboard: [pdfjs-c-performance][pdfjs-d-text-selection]
Depends on: 1054161
Yeah, this document mostly consists of moveText/showText pairs, where most of the showText ops display a single glyph. An example: > showText: [[{"fontChar":"I","unicode":"I","accent":null,"width":389}]] > moveText: [9.2,0] > showText: [[{"fontChar":"n","unicode":"n","accent":null,"width":666}]] > moveText: [15.6,0] > showText: [[{"fontChar":"t","unicode":"t","accent":null,"width":443}]] > moveText: [10.5,0] > showText: [[{"fontChar":"r","unicode":"r","accent":null,"width":443}]] > moveText: [10.4,0] > showText: [[{"fontChar":"o","unicode":"o","accent":null,"width":666}]] > moveText: [15.7,0] > showText: [[{"fontChar":"d","unicode":"d","accent":null,"width":666}]] > moveText: [15.7,0] > showText: [[{"fontChar":"u","unicode":"u","accent":null,"width":666}]] > moveText: [15.7,0] > showText: [[{"fontChar":"c","unicode":"c","accent":null,"width":666}]] > moveText: [15.7,0] > showText: [[{"fontChar":"t","unicode":"t","accent":null,"width":443}]] > moveText: [10.4,0] > showText: [[{"fontChar":"i","unicode":"i","accent":null,"width":333}]] > moveText: [7.8,0] > showText: [[{"fontChar":"o","unicode":"o","accent":null,"width":666}]] > moveText: [15.7,0] > showText: [[{"fontChar":"n","unicode":"n","accent":null,"width":666}]] > moveText: [15.7,0]
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 1224644
Resolution: --- → FIXED
Target Milestone: --- → Firefox 45
You need to log in before you can comment on or make changes to this bug.