Found the cause (or at least the main cause for SeaMonkey) today and spun off
a bug from the original bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1364977
Gave a test build to someone affected and it works. I hope the bug fix is ok.
If yes it will go into the final 2.48 for sure. ewong
On 7/05/2017 11:41 PM, WaltS48 wrote:
On 5/7/17 5:18 AM, Daniel wrote:
The latest Official release in SM 2.46 and there will, shortly
hopefully, be a SM 2.48 Beta release which will then become a SM 2.48
Release Version and then the SM 2.49 (Beta) will be the start of the
ESR versions.
Richmond wrote:
>
> https://archive.mozilla.org/pub/seamonkey/releases/
> https://archive.mozilla.org/pub/seamonkey/nightly/
>
> But there is a tinderbox build, which sounds like fun. :)
>
> https://archive.mozilla.org/pub/seamonkey/tinderbox-builds/comm-beta-linux/1494033293/
>
OK I was
Richmond wrote:
S Slicer wrote:
Francesco wrote:
Thanks.
I'll keep 2.50 since i can live with this bug After all it's the only one
i've found so far. Except for that, 64 bit 2.50 works really fine.
Francesco
Il giorno martedì 2 maggio 2017 18:56:16 UTC+2, Frank-Rainer Grahl ha scritto:
On 5/7/17 5:18 AM, Daniel wrote:
The latest Official release in SM 2.46 and there will, shortly
hopefully, be a SM 2.48 Beta release which will then become a SM 2.48
Release Version and then the SM 2.49 (Beta) will be the start of the
ESR versions.
SeaMonkey 2.48b1 was released on April 17,
Daniel wrote:
> On 7/05/2017 6:16 PM, Frank-Rainer Grahl wrote:
>> No I said. The logical step from aurora would switch to beta. Beta is
>> 2.51 at the moment. 2.50 is the current release.
>
> It should be stressed that these are Adrian's private releases ..i.e.
> Adrian has a SM 2.50 release
On 7/05/2017 6:16 PM, Frank-Rainer Grahl wrote:
No I said. The logical step from aurora would switch to beta. Beta is
2.51 at the moment. 2.50 is the current release.
It should be stressed that these are Adrian's private releases ..i.e.
Adrian has a SM 2.50 release version and a SM 2.51 Beta
No I said. The logical step from aurora would switch to beta. Beta is 2.51 at
the moment. 2.50 is the current release.
If you compile yourself clone comm-esr52 and apply the patch for bug 1353765:
https://bugzilla.mozilla.org/show_bug.cgi?id=1353765
This gives you 2.49.1 which has all security
> 2.49 and 2.50 profiles should be interchangeable
Same for 2.51
FRG
Frank-Rainer Grahl wrote:
No I said. The logical step from aurora would switch to beta. Beta is 2.51 at
the moment. 2.50 is the current release.
If you compile yourself clone comm-esr52 and apply the patch for bug 1353765:
Excuse me for still being confused. :)
I know you said to move to Adrian's beta, but where does he get the
source? I checked out comm-beta and compiled it, and it says 2.51. But I
see also there is a 2.48b1.
https://archive.mozilla.org/pub/seamonkey/releases/2.48b1/
So what have I ended up
S Slicer wrote:
> Francesco wrote:
>> Thanks.
>> I'll keep 2.50 since i can live with this bug After all it's the only
>> one i've found so far. Except for that, 64 bit 2.50 works really fine.
>>
>> Francesco
>>
>>
>> Il giorno martedì 2 maggio 2017 18:56:16 UTC+2, Frank-Rainer Grahl ha
>>
Francesco wrote:
Thanks.
I'll keep 2.50 since i can live with this bug After all it's the only one
i've found so far. Except for that, 64 bit 2.50 works really fine.
Francesco
Il giorno martedì 2 maggio 2017 18:56:16 UTC+2, Frank-Rainer Grahl ha scritto:
Looks like the x64 problem is a
Thanks.
I'll keep 2.50 since i can live with this bug After all it's the only one
i've found so far. Except for that, 64 bit 2.50 works really fine.
Francesco
Il giorno martedì 2 maggio 2017 18:56:16 UTC+2, Frank-Rainer Grahl ha scritto:
> Looks like the x64 problem is a bit older :)
>
>
Looks like the x64 problem is a bit older :)
https://bugzilla.mozilla.org/show_bug.cgi?id=393302
I wouldn't expect a solution soon.
FRG
Francesco wrote:
I can't find a 32 bit 2.50 release on akalla site, but maybe i'm missing
something.
Thanks
Francesco
Il giorno martedì 2 maggio 2017
Yes you are right. I would advise to stay with 2.49 and see if this one works.
I think he is preparing 2.49.1 from the ESR branch right now.
FRG
Francesco wrote:
I can't find a 32 bit 2.50 release on akalla site, but maybe i'm missing
something.
Thanks
Francesco
Il giorno martedì 2 maggio
I can't find a 32 bit 2.50 release on akalla site, but maybe i'm missing
something.
Thanks
Francesco
Il giorno martedì 2 maggio 2017 14:30:20 UTC+2, Frank-Rainer Grahl ha scritto:
> Interesting. Seems to be a problem with the x64 version only. First problem I
> ever encountered with the x64.
Interesting. Seems to be a problem with the x64 version only. First problem I
ever encountered with the x64. Please uninstall and try the x86 version. I
will need to look at the installer and see if something is wrong there.
FRG
Francesco wrote:
Il giorno sabato 29 aprile 2017 11:57:27 UTC+2,
Looks like a new bug. Its an easy way to crash 2.52a1 on Windows 7. It just
closes.
FRG
Francesco wrote:
Il giorno sabato 29 aprile 2017 11:57:27 UTC+2, Daniel ha scritto:
On 29/04/2017 4:55 PM, Francesco wrote:
Il giorno venerdì 28 aprile 2017 16:40:40 UTC+2, Daniel ha scritto:
On
On 2/05/2017 5:03 PM, Francesco wrote:
Il giorno sabato 29 aprile 2017 11:57:27 UTC+2, Daniel ha scritto:
On 29/04/2017 4:55 PM, Francesco wrote:
Il giorno venerdì 28 aprile 2017 16:40:40 UTC+2, Daniel ha
scritto:
On 28/04/2017 11:20 PM, Francesco wrote:
Il giorno lunedì 24 aprile 2017
Il giorno sabato 29 aprile 2017 11:57:27 UTC+2, Daniel ha scritto:
> On 29/04/2017 4:55 PM, Francesco wrote:
> > Il giorno venerdì 28 aprile 2017 16:40:40 UTC+2, Daniel ha scritto:
> >> On 28/04/2017 11:20 PM, Francesco wrote:
> >>> Il giorno lunedì 24 aprile 2017 15:05:33 UTC+2, TCW ha scritto:
>
On 1/05/2017 10:00 PM, TCW wrote:
On Sat, 29 Apr 2017 00:32:39 +1000, Daniel
wrote:
On 28/04/2017 8:25 PM, TCW wrote:
On Fri, 28 Apr 2017 15:45:05 +1000, Daniel
wrote:
On 28/04/2017 4:21 AM, TCW wrote:
On 4/24/17 8:05 AM, TCW wrote:
On 29/04/2017 4:55 PM, Francesco wrote:
Il giorno venerdì 28 aprile 2017 16:40:40 UTC+2, Daniel ha scritto:
On 28/04/2017 11:20 PM, Francesco wrote:
Il giorno lunedì 24 aprile 2017 15:05:33 UTC+2, TCW ha scritto:
Just saw it here
Il giorno venerdì 28 aprile 2017 16:40:40 UTC+2, Daniel ha scritto:
> On 28/04/2017 11:20 PM, Francesco wrote:
> > Il giorno lunedì 24 aprile 2017 15:05:33 UTC+2, TCW ha scritto:
> >> Just saw it here
> >>
On 28/04/2017 11:20 PM, surferjoe...@gmail.com wrote:
Il giorno lunedì 24 aprile 2017 15:05:33 UTC+2, TCW ha scritto:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Hello,
i installed this release and noticed that the
On 28/04/2017 8:25 PM, TCW wrote:
On Fri, 28 Apr 2017 15:45:05 +1000, Daniel
wrote:
On 28/04/2017 4:21 AM, TCW wrote:
On 4/24/17 8:05 AM, TCW wrote:
Just saw it here
Il giorno lunedì 24 aprile 2017 15:05:33 UTC+2, TCW ha scritto:
> Just saw it here
> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Hello,
i installed this release and noticed that the right click "send to mail
recipient" command doesn't
Frank-Rainer Grahl wrote:
> It is the same in Thunderbird. Mozilla changed locale apis. Might not be
> fixed
> completely for some time or ever. Tracked in Bug 1344594 and follow ups.
>
> Carl Kaufmann wrote:
>> TCW wrote:
>>> Just saw it here
>>>
No, only the aurora a2 channel has been discontinued by Mozilla. Looking at
recent code quality and other issues a mistake imho but telling the world how
stable the current release process became made a good press release and that
is all what seems to count :)
The logical step is to switch to
On 28/04/2017 4:21 AM, TCW wrote:
On 4/24/17 8:05 AM, TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Well, after quiet a bit of regular browser use, I am up to 1.2GB of RAM
use on SM 2.51b with one window
On 28/04/2017 5:30 AM, Frank-Rainer Grahl wrote:
The next releases after 2.48 will be from the ESR branch (2.49.x) for
some time. They will contain only bug and security fixes. The next
planned release after 2.49.x is 2.56 ESR. Depending on the fallout after
Firefox 57 it might never come to
Thank you, Thomas
Press CTRL-ALT-DEL (if you're using Windows) and click Task Manager.
Might also have to click on "Show Processes From All Users" to see it.
--
Pat Connors
http://www.connorsgenealogy.com
___
support-seamonkey mailing list
The next releases after 2.48 will be from the ESR branch (2.49.x) for some
time. They will contain only bug and security fixes. The next planned release
after 2.49.x is 2.56 ESR. Depending on the fallout after Firefox 57 it might
never come to this but we will see. The a2 aurora versions have
It is the same in Thunderbird. Mozilla changed locale apis. Might not be fixed
completely for some time or ever. Tracked in Bug 1344594 and follow ups.
Carl Kaufmann wrote:
TCW wrote:
Just saw it here
No. The devtools need a long look over and nobody found the time. Sorry :(
FRG
TCW wrote:
On 4/24/17 1:41 PM, EE wrote:
TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Do the language packs work, and is
On 4/24/17 8:05 AM, TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Well, after quiet a bit of regular browser use, I am up to 1.2GB of RAM
use on SM 2.51b with one window open.
While I would say that's a
TCW wrote:
On 4/27/17 12:55 PM, Pat Connors wrote:
TCW wrote:
Task manager will show current memory consumption.
I cannot find the 'task manager', I checked all the categories and do
not see it.
Press CTRL-ALT-DEL (if you're using Windows) and click Task Manager.
Might also have to click
On 4/27/17 12:55 PM, Pat Connors wrote:
TCW wrote:
Task manager will show current memory consumption.
I cannot find the 'task manager', I checked all the categories and do
not see it.
Press CTRL-ALT-DEL (if you're using Windows) and click Task Manager.
Might also have to click on "Show
TCW wrote:
Task manager will show current memory consumption.
I cannot find the 'task manager', I checked all the categories and do
not see it.
--
Pat Connors
http://www.connorsgenealogy.com
___
support-seamonkey mailing list
On 4/27/17 4:34 AM, Richmond wrote:
Paul B. Gallagher wrote:
TCW wrote:
On Wed, 26 Apr 2017 13:32:05 -0700, Pat Connors
wrote:
Leaky as in memory leakage. 2.48 and 2.49 were leaky for me.
During the course of the day memory usage would just go up and up
and never be
Paul B. Gallagher wrote:
> TCW wrote:
>
>> On Wed, 26 Apr 2017 13:32:05 -0700, Pat Connors
>> wrote:
>>
Leaky as in memory leakage. 2.48 and 2.49 were leaky for me.
During the course of the day memory usage would just go up and up
and never be freed up until
TCW wrote:
On Wed, 26 Apr 2017 13:32:05 -0700, Pat Connors
wrote:
Leaky as in memory leakage. 2.48 and 2.49 were leaky for me.
During the course of the day memory usage would just go up and up
and never be freed up until I was consuming 1-2GB RAM. 2.50beta
was fine the
Leaky as in memory leakage. 2.48 and 2.49 were leaky for me. During
the course of the day memory usage would just go up and up and never
be freed up until I was consuming 1-2GB RAM. 2.50beta was fine the
2.50 release brought back the leakiness. I just switched to the 2.51
beta this morning
On 4/26/17 1:32 PM, Pat Connors wrote:
I have found this final version of Adrian's 2.50 leaky as the previous
versions were. The 2.50 beta from March seemed better. I was able to
crash 2.50 after it had consumed 1+GB of RAM and then measuring memory
but even with 2.50 beta, I was always
I have found this final version of Adrian's 2.50 leaky as the previous
versions were. The 2.50 beta from March seemed better. I was able to
crash 2.50 after it had consumed 1+GB of RAM and then measuring memory
but even with 2.50 beta, I was always stable.
What does 'leaky' mean?
I have
On 4/24/17 4:24 PM, S Slicer wrote:
TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
The last 64- bit version that worked for me was 2.45!
I even uninstalled all add-ons, and v2.50, like the others after
On 4/25/17 8:04 AM, Richmond wrote:
Frank-Rainer Grahl writes:
Depending on the fallout after Firefox 57 this might be a dead end so please
back up you 2.49 profile. The next official version after 2.48 will be 2.49.1
from the ESR channel.
2.50 still has a notification bug
Frank-Rainer Grahl writes:
> Depending on the fallout after Firefox 57 this might be a dead end so please
> back up you 2.49 profile. The next official version after 2.48 will be 2.49.1
> from the ESR channel.
>
> 2.50 still has a notification bug which isn't bad but noticeable:
>
TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
It changed the date format in mail/news on my system (Windows 10, x64),
from ISO8601 (-MM-DD) to US standard (MM/DD/YY), and I see no way to
change it to
TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
The last 64- bit version that worked for me was 2.45!
I even uninstalled all add-ons, and v2.50, like the others after v2.45,
crashed every time I tried to
On 4/24/17 1:41 PM, EE wrote:
TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Do the language packs work, and is the problem with the devtools
eyedropper fixed yet?
Only one way to find out. ;-)
TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
Do the language packs work, and is the problem with the devtools
eyedropper fixed yet?
___
support-seamonkey mailing
2.50 will not work on Vista/Server 2008 or XP/Server 2003/XP64.
FRG
TCW wrote:
On 4/24/17 8:27 AM, WaltS48 wrote:
On 4/24/17 9:05 AM, TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
He isn't going to
On 4/24/17 8:27 AM, WaltS48 wrote:
On 4/24/17 9:05 AM, TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
He isn't going to follow the ESR channel so WindowsXP and Vista users
can use his builds?
Hard to
Depending on the fallout after Firefox 57 this might be a dead end so please
back up you 2.49 profile. The next official version after 2.48 will be 2.49.1
from the ESR channel.
2.50 still has a notification bug which isn't bad but noticeable:
On 4/24/17 9:05 AM, TCW wrote:
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
He isn't going to follow the ESR channel so WindowsXP and Vista users
can use his builds?
--
Go Bucs and Pens!
Coexist
Just saw it here
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows64/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
56 matches
Mail list logo