Stop writing compatibility.ini piecemeal and on the main thread and on startup
Categories
(Toolkit :: Startup and Profile System, task, P3)
Tracking
()
Performance Impact | medium |
People
(Reporter: Gijs, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(4 keywords, Whiteboard: [fxperfsize:M])
+++ This bug was initially created as a clone of Bug #1541491 +++
If we decide in 1541491 that we need to keep compatibility.ini, nsAppRunner.cpp's WriteVersion should stop writing it in 20-odd increments, and write the entire (short) file out at once, and off-main-thread, after startup.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
(In reply to :Gijs (he/him) from comment #0)
+++ This bug was initially created as a clone of Bug #1541491 +++
If we decide in 1541491 that we need to keep compatibility.ini, nsAppRunner.cpp's WriteVersion should stop writing it in 20-odd increments, and write the entire (short) file out at once, and off-main-thread, after startup.
If we're writing it off-main-thread then we should probably at least truncate it or something immediately so if the write never succeeds the next run knows that the profile has been modified in some way.
Reporter | ||
Comment 2•5 years ago
|
||
(In reply to Dave Townsend [:mossop] (he/him) from comment #1)
If we're writing it off-main-thread then we should probably at least truncate it or something immediately so if the write never succeeds the next run knows that the profile has been modified in some way.
We could block shutdown on writing it...
Comment 3•5 years ago
|
||
(In reply to :Gijs (he/him) from comment #2)
(In reply to Dave Townsend [:mossop] (he/him) from comment #1)
If we're writing it off-main-thread then we should probably at least truncate it or something immediately so if the write never succeeds the next run knows that the profile has been modified in some way.
We could block shutdown on writing it...
That's great, unless we crash.
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Description
•