Am Samstag, 5. Juli 2014 14:21:47 UTC+2 schrieb David Rajchenbach-Teller:
[...]
3. Crash report is stored to disk, without any dialog;
4. If the crash happened during Firefox shutdown, do nothing, otherwise
restart Firefox to its previous state (obviously, we need some measure
to prevent this
Something new to this ???
Greets, Tobias.
Am Dienstag, 1. Juli 2014 21:44:16 UTC+2 schrieb Tobias Besemer:
Am Dienstag, 1. Juli 2014 14:05:39 UTC+2 schrieb David Rajchenbach-Teller:
Let's concentrate on Session Restore for the moment.
OK, it was just because of the example
Am Sonntag, 6. Juli 2014 11:08:22 UTC+2 schrieb Neil:
Since Session Restore already knows things such as the size and position
of the window it wants to restore, [...]
Some experiences from Win7 64bit:
- During use of FF, FF sometimes reorder the windows in my Taskbar.
- FF saves the size of
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
2) Being able to integrate the crash-submission flow into the browser
opens up possibilities for better UX and features, since it's the
familiar cross-platform environment we all work in.
Sorry, maybe a little bit OT ... ;-)
As far as I can remember, at the beginning when GRE was build, there was the
try that Firefox/Thunderbird/Mozilla-Suite will use this ...
After Thunderbird is now back, a Mozilla Update Service exist and the Crash
Reporter needs to be re-done, but keeps a standalone App for startup problems
of
Am Dienstag, 8. Juli 2014 20:40:13 UTC+2 schrieb Justin Dolske:
On 7/8/14 9:56 AM, Tobias Besemer wrote:
Am Dienstag, 8. Juli 2014 18:23:00 UTC+2 schrieb Justin Dolske:
2) Being able to integrate the crash-submission flow into the browser
opens up possibilities for better UX
Am Dienstag, 1. Juli 2014 14:05:39 UTC+2 schrieb David Rajchenbach-Teller:
Let's concentrate on Session Restore for the moment.
OK, it was just because of the example and the need for a Journaled Storage
...
Adopting a Journaled Storage will let us decrease the total amount of
I/O. Once we
Am Dienstag, 1. Juli 2014 21:22:17 UTC+2 schrieb Zack Weinberg:
On 06/28/2014 08:12 AM, Tobias Besemer wrote:
Forgetting closed pages - or the data to a page - would only be a
problem is a scenario like this: The user editing a large text in
a wiki, don't save it, close the page
Am Samstag, 28. Juni 2014 18:39:12 UTC+2 schrieb David Rajchenbach-Teller:
I don't follow what you have in mind. Assuming that you suggest we move
to sqlite, you seem to be suggesting that we should considerably
increase the amount of I/O. Or do I misunderstand what you say?
At first it was
I often restart FF because of memory use bloat - a restart cleans up that
memory use somewhat. When I do that I expect all my history for each tab to
be retained, and to be able to undo closed tabs.
History would be retained, old form data would be cleared, closed tabs would be
forgotten,
Am Samstag, 28. Juni 2014 07:28:22 UTC+2 schrieb Katelyn Gadd:
If this behavior were changed I'd change it back locally with a pref
or addon or something.
This should be the solution for those who want this behavior.
There are lots of reasons to exit (powering off to install
windows
Am Samstag, 28. Juni 2014 08:04:43 UTC+2 schrieb Tim Taubert:
To properly set the stage for this discussion, why exactly do you want
this? Where do you see the problem with a big sessionstore.js file?
Bug 669034 - (sessionRestoreJank) [meta] Re-architect session restore to avoid
periodic
OK, maybe we should first talk about what the ss is for, what he should do,
when it is used so ...
The ss is necessary, when e.g. a user editing a large text in a wiki, haven't
saved that text yet, and closes this page as a mistake. So he can go back /
undo close and still have his un-saved
Am Samstag, 28. Juni 2014 14:00:12 UTC+2 schrieb Tim Taubert:
Why is the amount of I/O a problem for you exactly?
The amount of I/O is always a problem! E.g. for Notebooks in battery use.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
Am Samstag, 28. Juni 2014 14:03:38 UTC+2 schrieb David Rajchenbach-Teller:
I am currently running benchmarks to find the influence of each part of
Session Restore data on startup duration.
Thank you!
The work is ongoing, but for
the moment, I can confirm that closed tabs and closed windows
Am Samstag, 28. Juni 2014 14:23:32 UTC+2 schrieb Tim Taubert:
Tobias Besemer wrote:
The ss is necessary, when e.g. a user editing a large text in a wiki,
haven't saved that text yet, and closes this page as a mistake. So he can
go back / undo close and still have his un-saved text
Am Samstag, 28. Juni 2014 14:25:35 UTC+2 schrieb Tim Taubert:
Tobias Besemer wrote:
The amount of I/O is always a problem! E.g. for Notebooks in battery use.
Yes, of course. That is a known problem and we're working on it by
increasing the write interval when running on battery and working
Am Samstag, 28. Juni 2014 14:42:40 UTC+2 schrieb David Rajchenbach-Teller:
See bug https://bugzilla.mozilla.org/show_bug.cgi?id=956713 for details
on the proposed Journaled Storage mechanism. This should bring down the
number of writes by an order of magnitude.
Thx! I will try to study it ...
Am Samstag, 28. Juni 2014 14:45:38 UTC+2 schrieb David Rajchenbach-Teller:
While we should and will reduce the total amount of I/O due to Session
Restore, I must add that we have not attempted to compare it to the
total amount of I/O due to cache access for instance. I would not be
surprised
Am Samstag, 28. Juni 2014 14:44:53 UTC+2 schrieb Tim Taubert:
Tobias Besemer wrote:
It is not just a question of battery!
Too much writing accesses also harms the life-time of HDs or SSDs!
Yup, that's why we're working on it. Clearing data on quit won't get us
there as data accumulates
Am Samstag, 28. Juni 2014 14:45:38 UTC+2 schrieb David Rajchenbach-Teller:
Tobas, if you have an opportunity to perform a comparison, this would be
an interesting piece of data.
Sorry, not yet ... :-/
___
dev-platform mailing list
Am Samstag, 28. Juni 2014 14:42:40 UTC+2 schrieb David Rajchenbach-Teller:
See bug https://bugzilla.mozilla.org/show_bug.cgi?id=956713 for details
on the proposed Journaled Storage mechanism. This should bring down the
number of writes by an order of magnitude.
I had a look at this bug ...
Am Samstag, 28. Juni 2014 16:45:39 UTC+2 schrieb Tobias Besemer:
Am Samstag, 28. Juni 2014 14:42:40 UTC+2 schrieb David Rajchenbach-Teller:
See bug https://bugzilla.mozilla.org/show_bug.cgi?id=956713 for details
on the proposed Journaled Storage mechanism. This should bring down
A new topic to move the discussions from the bugs to this group.
Bug 669034 - (sessionRestoreJank) [meta] Re-architect session restore to avoid
periodic freezes
https://bugzilla.mozilla.org/show_bug.cgi?id=669034
Bug 810932 - Investigate how to redesign sessionstore.js for improved
performance
24 matches
Mail list logo
