DjVu wastes lots of hours before failing (repeatedly) on large items
Bug #174318 reported by
Hank Bromley
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Deriver |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
If item is too large, DjVu fails, but only after running for many hours, and does so repeatedly due to deriver looping.
Make it fail more gracefully: identify the threshold for failure, and if item exceeds that size, exit without running.
(A separate bug report pertains to actually fixing DjVu so it can handle larger items.)
| Changed in deriver: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Hank Bromley (hank-archive) wrote | #1 |
To post a comment you must log in.
When DjVu doesn't complete successfully, the deriver doesn't make djvu.txt (even if DjvuXML successfully created djvu.xml). So, either:
1) change the DJVUTXT module so it can run even if DjVu hasn't succeeded, so long as DjvuXML has, or
2) use ~hank/bin/