OS/2, eCS & ArcaOS - General > Events
Firefox problem, was Re: IRC speakup with BWW this Saturday (3 of March)!
David Graser:
I was looking at a utility called highmem
http://www.os2site.com/sw/dev/util/highmem-20140406-os2.zip
Its developer "Yuri Dario (Paperino)" states the following:
"Loading code high should almost always be ok. That's because loading code high is mostly transparent to applications: it's the kernel's job to map high addresses to the physical memory where the code resides. Unless some code tries to map a linear code address (aka: a function pointer) to a segmented code address, see below but that does not happen very often.
For loading data high this is much more critical: of course, the same applies as for code but remember "thunking"? A lot of APIs make the silent assumption that a linear data address can be easily mapped to a segmented address and vice versa by a simple well known "thunking" algorithm. However that algorithm only works for "low memory". And OS/2 has enough 16-bit code in its bowels that can only access data via a segmented data address. If you have a big application like Firefox you never know if there is some low level OS component that makes that simple assumption, thunks a data address and subsequently gets it wrong if "high memory" data addresses are used."
This looks like what Firefox is doing.
Dave Yeo:
We've been pretty careful to make sure any 16 bit API is called from low memory. Doesn't mean it doesn't happen but it sure happens a lot less then when this move to high memory started.
Unluckily, there are also problems in the kernel with high loaded code and data. Most of the recent kernels have been attempts to fix this but without the source code and the right to rebuild and distribute fixes kernels...
David Graser:
I made a STARTUP.CMD file and put it into my ArcaOS 5.02 root directory.
@ echo off
x:
md temp
exit
which creates a temp directory on drive X which is my RAM drive.
I then changed my config.sys to point to where my new temporary directory is located.
SET TMP=x:\\temp
SET TEMP=x:\temp
SET TMPDIR=x:\temp
Now the problem.
My Firefox 45.9.0 download directory in Options points to
f:\home\temp
When I download a file, it always fails. When I click the retry, it shows it finishes the download.
However,the downloaded file is not found in the f:\home\temp directory.
I now find it in my X:\temp directory.
Before, Firefox would have no problem downloading and the downloads would always be found in the home\temp directory.
Have I done something wrong or is this a problem with Firefox?
ivan:
Out of interest make a 'F:\home\download' directory and point the firefox downloads to that. If it works everything is good.
I think the problem could be in the way the temp setting is handled.
David Graser:
I made a mistake. Firefox points to the download directory which is in the home directory. The download directory does exist.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version