Open Bug 1356879 Opened 7 years ago Updated 10 months ago

Timestamp "lastAccessed" written too often to File "recovery.js"

Categories

(Firefox :: Session Restore, defect)

51 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: VBatT_SW, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxperf:p5])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

Whenever a browsed document is shifted up/down, even just a few millimeter - 
the timestamp "lastAccessed" of that URI is written to the file "recovery.js". 



Actual results:

Problem: 
1) Performance  - AV Realtime Scanner is aktiv too often
2) SSD  - they don't like too many write operations 



Expected results:

Could the timestamp be written 
- when site is opened: to file
- when FireFox is closed:  to file 
- else: only to system memory
?
Blocks: ss-perf
Component: Untriaged → Session Restore
Whiteboard: [fxperf]
Difficult to give this a high priority without seeing a profile where it has a meaningful impact. I think this is the kind of things that will greatly benefit from switching session restore to an LMDB key value store.
Whiteboard: [fxperf] → [fxperf:p5]
I've hoped to use this field to detect user interaction, and for inactive tabs that worked well, but if tab is active, value is changing on every tab event (caused by loading process, no user interaction at all).

What is semantics of lastAccessed? Documentation on https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/tabs/Tab is vague.
This field is updated at least 20 times during loading of JIRA tracking system page. It could be updated more often, but it's difficult to observe such changes from WebExtensions land.
Blocks: 1304389
No longer blocks: ss-perf
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 17 votes.
:dao, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Flags: needinfo?(dao+bmo)

I can't reproduce this on Linux with Firefox 105. File "recovery.jsonlz4" is not rewritten whenever I scroll.

You need to log in before you can comment on or make changes to this bug.