Closed
Bug 44563
Opened 26 years ago
Closed 24 years ago
Optimization: Disable timebomb code for Mozilla
Categories
(SeaMonkey :: General, defect, P3)
SeaMonkey
General
Tracking
(Not tracked)
Future
People
(Reporter: BenB, Assigned: leaf)
Details
(Keywords: helpwanted, memory-footprint)
Timebombs make no sense in an open-source project. I might want to use an older
build. Why shouldn't I? I posted this question to .seamonkey and .general, but
nobody nad a good answer. So, please disable them. (Leaving the code in the
repository and is completely fine, as vendors might want to use them.)
| Reporter | ||
Comment 1•26 years ago
|
||
See <news://news.mozilla.org/39626FFC.A291C7A6@montage.ca> for a good reason to
disable them.
Comment 3•26 years ago
|
||
They are controled via prefs.
marking invalid.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
please excuse my ignorance, what prefs? where? how does one go about undoing
the time bomb? or preventing it from being activated?
Comment 5•26 years ago
|
||
| Reporter | ||
Comment 6•26 years ago
|
||
OK, it doesn't seem to be enabled for Mozilla. That's very good.
But why is it built and run?
I have a
user_pref("timebomb.first_launch_time", "962840675265210");
in my prefs.js, and if I delete it, it is rewritten as soon as I start Mozilla.
Timebombs make no sense for Mozilla and propably also for most commercial stable
releases. Running the code costs unnecessarily time and disk/download footprint.
Adjusting SUMMARY and REOPENing as optimization bug.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: Disable timebombs for Mozilla → Disable timebomb code for Mozilla (optimization)
| Reporter | ||
Updated•26 years ago
|
Summary: Disable timebomb code for Mozilla (optimization) → Optimization: Disable timebomb code for Mozilla
Comment 9•25 years ago
|
||
we won't need this code in the embedding case either
Comment 10•25 years ago
|
||
It *is* optional.
Updated•25 years ago
|
Whiteboard: [nsbeta3+]
Comment 11•25 years ago
|
||
this code is used from seamonkey's main function (which never gets called for
embedding) in a component that embedding doesn't load. Taking off embedding
radar.
-> Trudelle. Peter, we don't want to ship the final product w/ this.
| Assignee | ||
Comment 13•25 years ago
|
||
I believe a timebomb that is so easily disabled is ideal for open source binary
non-final releases.
If you really, really want to run old builds, you can (with the help of a text
editor).
As for a ``final'' product not having a timebomb; to which final product are you
alluding, jud? the betas? the milestones? The mozilla release (whenever whatever
it will be ships)? I guess i'll agree that the ``real'' mozilla release, if ever
there is one, shouldn't have this.
I guess we can add a configure option/env variable to enable or disable this as
part of the build. Leaving helpwanted keyword, because i'm not going to have
time to make this do the right thing in the short term future.
Comment 15•25 years ago
|
||
rtm-
mozilla-specific. timebombs are already disabled in the ns build, we're not
removing the timebomb code from the ns build. not holding netscape rtm for this
bug.
Whiteboard: [rtm-]
Comment 16•25 years ago
|
||
I first saw this one today in my prefs.js (created a new profile approx. two
weeks ago) so obviously it's still added to new profiles. Thus it's not
disabled.
I think even the words "timebomb" scares the user away. How am I supposed to
know what a timebomb is, in Mozilla code?
Comment 17•24 years ago
|
||
This bug has been fixed by removing nsTimebomb from the build (see bug 57306)
Comment 18•24 years ago
|
||
true. cc blake to verify.
Status: NEW → RESOLVED
Closed: 26 years ago → 24 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 19•24 years ago
|
||
Hakan, this is not invalid!
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 20•24 years ago
|
||
Sorry, doesn't the removal of the timebomb stuff render this bug invalid?
| Reporter | ||
Comment 21•24 years ago
|
||
No, since the "bug" existed when I filed it. It is WFM, DUP or FIXED (if it is
really fixed).
Comment 22•24 years ago
|
||
Sigh, who cares. The important part is that it's resolved, not how.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 24•24 years ago
|
||
*** This bug has been marked as a duplicate of 57306 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•