home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!paperboy.micro.umn.edu!magnus.acs.ohio-state.edu!csn!teal!raney
- From: raney@teal.csn.org (Scott Raney)
- Subject: Re: Max Property size
- Message-ID: <raney.727920003@teal>
- Sender: news@csn.org (news)
- Nntp-Posting-Host: teal.csn.org
- Organization: Colorado SuperNet, Inc.
- References: <NOSMO.93Jan24142141@nov8.ximage.com>
- Distribution: comp.window.x
- Date: Mon, 25 Jan 1993 00:00:03 GMT
- Lines: 26
-
- nosmo@nov8.ximage.com (Vince Kraemer) writes:
-
-
- >Is there a way to determine the maximum size of a property that is
- >allowed on server? I have selections which may be large and would like
- >a way to find out sooner (before I generate a Alloc error) rather than
- >later.
-
- The problem is worse than you realize: trying to get a large property
- (more than 64K) from an IBM RS/6000 server causes the console to lock
- up, requiring a reboot to clear (releases 3.2.2 and earlier, at
- least). We've run into a 64K limit on other systems as well, so I
- consider 64K the maximum safe size.
-
- The limit may be smaller on some servers, however, and I don't know
- how to tell when it's going to be a problem. This problem is
- especially serious on PC and Mac X-servers which are prone to memory
- management woes.
-
- >thanks
- >vbk
- --
- ***********************************************************************
- * Scott Raney 303-447-3936 Remember: the better you look, *
- * raney@metacard.com the more you'll see -- Lidia *
- ***********************************************************************
-