Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Very long time to open/ show a specific PDF file

未关闭
#693 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
c, linux

调研方向

首先,在 Linux Mint 21.3 上使用 XReader 4.0.2,通过附加的 Killer_PDF_toom-Anleitung-PDF.pdf 重现延迟,然后将其打开时间与报告中提到的 viewer 进行比较。该 issue 提到了渲染、CPU 使用率和缺少进度反馈,但没有列出源文件或测试;完成的标准应是可测量的改进,或明确的忙碌状态反馈。

由索引模型根据 Issue 内容生成。

描述

Distribution

Linux Mint 21.3 Cinnamon

Package version

4.0.2

Frequency

Always

Bug description

A specific PDF file (attached) needs minutes to be shown - is seems to be (very) complex to render.
XReader uses only ONE of EIGHT available Threads of my Intel i7-4702MQ CPU @8GB RAM (Fujitsu Lifebook E744) - so the time could be much shorter using all available resources.
User without looking at CPU load could think XReader hung up.

Steps to reproduce

Just open the attached PDF "Killer_PDF_toom-Anleitung-PDF.pdf"

Expected behavior

Better performance from End-user-point-of-view.
Usage of all free HW resources
Visual information about opening process (progress bar) to show XReader is busy

Benchmark Testing

XReader (4.0.2) needs 150s to open the file, all pages immediately accessible

Brave (142.1.84.141) needs 90s to show first page, but additional time to show new page (even it it was shown already before)

Okular (Flatpak 25.08.2) needs 170s to open the file completely. Before that new pages needs 20s to be shown properly

Firefox (145.0) needs less than 15s, all pages immediately accessible.

Master PDF Editor (5.9.94) needs 15s to open the file, but additional 2s per new page.

Xournal (Flatpak 1.2.8) needs 70s to open the file, all pages immediately accessible.

Firefox performs by far the best.

Killer_PDF_toom-Anleitung-PDF.pdf

Additional information

It seems none of the PDF viewers mentioned above uses more than one CPU thread - so here is potentially big room for improvement.

主要语言
C
星标
283
派生
82
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

linuxmint/xreader 的其他 Issue

查看 linuxmint/xreader 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。