Closed
Bug 516794
Opened 15 years ago
Closed 15 years ago
XULRunner reports "Not enough memory available to start Fennec." even with substantial available memory
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
ARM
Windows Mobile 6 Professional
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: brian, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: http://download.mozilla.org/?product=fennec-1.0a3&os=winmo&lang=en-US
Attempting to run Fennec 1.0 alpha 3 for Windows Mobile; memory utility reports > 64 MB of Program memory *free*.
I tried installing Fennec 1.0 a3 in main memory first, then uninstalled and tried on the storage card. In both cases, the XULRunner error "Not enough memory available ..." appeared even with nothing else running and > 64 MB program memory available. When rebooting the phone, the same error appeared on startup even before SPB Mobile Shell had launched.
Fennec shouldn't actually require more memory than this phone has available ...
Reproducible: Always
Steps to Reproduce:
1. Attempt to launch Fennec
Actual Results:
XULRunner error: "Not enough memory available to start Fennec."
Expected Results:
Fennec should launch
HP iPAQ 614c Business Navigator
Processor Type: ARM920T PXA270
Processor Revision: C5
System Memory: 256 MB ROM/128 MB RAM
Display: 240 x 320, 65535 colors
OS: Windows Mobile 6 Professional - CE OS 5.2.1620 (Build 18125.0.4.2)
Other running software: SPB Mobile Shell
Reporter | ||
Updated•15 years ago
|
OS: Other → Windows Mobile 6 Professional
Hardware: Other → ARM
I have exactly the same problem.
samsung i788 (same to i780)
os:wm 6.5 23420
please notice it
Comment 3•15 years ago
|
||
That error messages indicates that we failed to dynamically load either xul.dll or xpcom.dll and the system tells us the problem is there is not enough memory available. My xul.dll is 24Mb with symbols, so it seems your device has considerably less than 64Mb of RAM available.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 4•15 years ago
|
||
Leaving aside that at 24 MB, that file alone would be twice the size of my entire Opera Mobile installation, and even the 13.6 MB version I have is several times the size of most entire app installs on a mobile platform, Settings/Memory is reporting 30 MB storage memory and 63 MB program memory free at the moment. I have tried removing additional programs, etc. to free up more storage than that in the past, too. The total installation of Fennec is clocking in at about 25.5 MB, so I should be able to entirely duplicate it in storage and load several copies in RAM given the available memory on the system at present. Instead, I get this error. If you want to make the case that Fennec is ridiculously large for a mobile app and needs to be trimmed down to a more reasonable size, I'd back you up on that. But it's not larger than my available memory.
Comment 5•15 years ago
|
||
I think the difference here is storage memory vs runtime memory (RAM). We are targeting devices with >=128MB of available RAM. We know we have a lot of problems on devices with 96MB of RAM.
Status: RESOLVED → VERIFIED
Updated•15 years ago
|
Component: Windows Mobile → General
QA Contact: mobile-windows → general
Assignee | ||
Updated•11 years ago
|
tracking-fennec: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•