Ticket #613 (new enhancement)

Opened 4 years ago

Last modified 8 months ago

check that browse flushes caches when memory gets tight

Reported by: tomeu Owned by: erikos
Priority: Unspecified by Maintainer Milestone: 0.94
Component: Browse Version: Unspecified
Severity: Unspecified Keywords:
Cc: cjb, bernie, godiard, humitos Distribution/OS: Unspecified
Bug Status: New

Description

if it doesn't, Browse could listen for /dev/mem_notify getting readable and call FlushCaches or whatever it is called.

Change History

Changed 4 years ago by tomeu

  • milestone changed from Unspecified by Release Team to 0.86

Changed 4 years ago by erikos

  • type changed from defect to enhancement
  • status_field changed from Unconfirmed to New

Changed 4 years ago by tomeu

  • cc cjb, bernie added
  • milestone changed from 0.86 to 0.88

Actually /dev/mem_notify nor anything similar has gotten yet into the kernel. Hope that for 0.88...

Changed 3 years ago by walter

  • milestone changed from 0.88 to 0.90

Changed 2 years ago by RafaelOrtiz

Could help also for #2659

Changed 2 years ago by RafaelOrtiz

  • milestone changed from 0.90 to 0.94

Moving to 0.94 as it is our next release. ;).

Changed 2 years ago by RafaelOrtiz

The change made for v122 for #2659, can help improve these situation.

Changed 9 months ago by humitos

  • cc godiard, humitos added

Is still this ticket valid? Can I close it as obsolete?

Changed 9 months ago by godiard

Can you check if Browse keep files in any temp directory or remove them all at close?

Changed 8 months ago by humitos

Well, there are two (at least) different caches on WebKit.

  1. Page Cache: this one is to keep in memory the back and forward page. We are not using this one at the moment.
  2. On Disk Cache: this cache keeps file on the hard disk to load web pages faster. This is implemented using libsoup (SoupCache), but it seems that we are not using this. I didn't find any related to this:
Note: See TracTickets for help on using tickets.