On Thu, Nov 13, 2008 at 10:38:08PM +0100, Johan Solve wrote: > > Here's an earlier discussion about this, with an authoritative answer: > http://www.listsearch.com/BBEdit/Thread/index.lasso?4878#22517 > > At 15.12 -0500 2006-11-12, Rich Siegel wrote: > >Because of a limitation in the OS, the largest file size we can > >currently read is 768M when represented as Unicode. Note the > >qualification; since BBEdit represents files internally as Unicode, a > >character takes up two bytes, so today's practical limit is 384M on > >disk (since that'll expand to 768M when represented as Unicode). > >Working around the limitation is on our to-do list.
OK, that is not so much a limitation as its a deliberate limit imposed by the OS to prevent a process from claiming all the system resources. For example the default in FreeBSD is 512MB per process. It can be overridden with a kernel tuning parameter. Perhaps the same is true of MacOS X? OTOH I wouldn't recommend it for casual use. Some of the tables a kernel allocates for tracking resources are statically allocated at boot time for efficiency and to make sure they exist. The larger the allowed max process size the larger the process tables have to be to track memory allocated to the process. All processes no matter how small have to have these large tables because one never knows how large the process will grow. So the larger the process memory size limit the more overhead is used tracking all processes and/or threads. -- David Kelly N4HHE, [EMAIL PROTECTED] ======================================================================== Whom computers would destroy, they must first drive mad. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a specific feature request or would like to report a suspected (or confirmed) problem with the software, please email to "[EMAIL PROTECTED]" rather than posting to the group. -~----------~----~----~----~------~----~------~--~---
