Feb 27 Build
-
- Posts: 199
- Joined: December 16th, 2002, 4:44 pm
- Location: Ottawa, Canada
-
- Posts: 364
- Joined: January 1st, 2003, 1:28 pm
- Location: Lincoln, NE
This build has a big problem with java windows, too. If I try to click (say a download link) on anything in a java popup window, Phoenix 20030227 crashes immediately. It also has a problem with large downloads, for example, any file over a MegaByte or so. Which may also explain why some people are crashing when they try to download a new build from the ftp server using the 20030227 build.
- nilson
- Posts: 4100
- Joined: February 15th, 2003, 11:55 pm
- Location: Tuscaloosa, Alabama
- Contact:
-
- Posts: 5
- Joined: December 18th, 2002, 11:08 pm
- Spewey
- Folder@Home
- Posts: 5799
- Joined: January 25th, 2003, 2:06 pm
- Location: St. Paul, Minnes°ta
I disagree. I am powering through it. I had problems earlier, but I blame it on a flash page and an instance somehow got left in memory. My profiles and basically everything got screwed up until I checked Task Manager and foun a 23MB invisible instance of Px running. (W2K)
Javascript works. Themes and extensions work. Haven't d/l'd anything yet. I will try after this post.
I dunno, I ain't giving up yet.
UPDATE: Double reconfirming "Px appears to close but stays in memory and allows a new instance to arise appearing normal". Also, d/l from above moz site--->Px hang.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030227 Phoenix/0.5
Javascript works. Themes and extensions work. Haven't d/l'd anything yet. I will try after this post.
I dunno, I ain't giving up yet.
UPDATE: Double reconfirming "Px appears to close but stays in memory and allows a new instance to arise appearing normal". Also, d/l from above moz site--->Px hang.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030227 Phoenix/0.5
-
- Posts: 199
- Joined: December 16th, 2002, 4:44 pm
- Location: Ottawa, Canada
Spewey wrote:[...]an instance somehow got left in memory. My profiles and basically everything got screwed up until I checked Task Manager and foun a 23MB invisible instance of Px running. (W2K)
That happened to me once too with the Win32 2/27 build, with WinXP Pro SP1. It was using only about 2500Kb of memory, though.
-
- Posts: 199
- Joined: December 16th, 2002, 4:44 pm
- Location: Ottawa, Canada
-
- Moderator
- Posts: 3275
- Joined: November 6th, 2002, 12:07 pm
- Location: Federal Republic of Germany
Re: virual memory problems
Mika wrote:I get a memory overload on sometimes. Memory is raising up to 130 mb (by 196 mb ram) and then I have to terminate the process.
I am using Windows XP.
PX used 60MB of RAM the other day (02-26 build), never experienced this before...
just installed the 02-27 nightly now.
edit: phoenix.exe process continues after closing the program, cant download any files.....
- djk
- Posts: 219
- Joined: November 5th, 2002, 6:06 am
- Location: SC, USA
download crashing....
Anyone have any idea when the download crash/hang started to happen?
Px build 20030225 has an upgrade to the download dialog, which actually broke it (bug 194921). Bug 194921's fix first appeared in the 20030226 builds of px.
Maybe one or both of these checkins broke px downloading?
Here is the CVS log for (what I believe is) the appropriate file:
http://bonsai.mozilla.org/cvslog.cgi?fi ... t=/cvsroot
I'll just stay with 20030224 for now.
Px build 20030225 has an upgrade to the download dialog, which actually broke it (bug 194921). Bug 194921's fix first appeared in the 20030226 builds of px.
Maybe one or both of these checkins broke px downloading?
Here is the CVS log for (what I believe is) the appropriate file:
http://bonsai.mozilla.org/cvslog.cgi?fi ... t=/cvsroot
I'll just stay with 20030224 for now.