xreader allocates 100GB + 2 * 80GB WebKit

Open
#530 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start by reproducing the issue with a local PDF document and observe xreader, WebKitWebProcessor, and WebKitNetworkProcessor memory usage. Investigate why these processes allocate roughly 100 GB, 80 GB, and 80 GB, then verify that rendering the 2 MB text-only PDF no longer causes unjustified allocations or unnecessary network processing.

Written by the indexing model from the issue text.

Description

 * Xreader version 2.8.2
 * Distribution - Mint 20.1

Issue
xreader allocates 100 GB VM for itself.
In addition, it starts a WebKitWebProcessor at 80 GB and a WebKitNetworkProcessor at another 80 GB

Steps to reproduce
Open any local PDF document

Expected behaviour
Allocate the amount of memory needed to render the document. Even if this menory is virtual and possibly unreserved and not prepopulated, then still the sheer size is hard to justify as a need to render a 2 MB text-oinly PDF.

Other information
xreader is a local PDF viewer and the menu provides no options to access remote files. For this reason, I do not understand why it starts WebKit network processors.

Dominant language
C
Stars
283
Forks
82
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/xreader

All issues in linuxmint/xreader

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.