[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

3296.0. "bitmap too large?" by TPOVC::JOHNNYHO () Mon Sep 03 1990 07:45

    A customer tried to create many bitmap but will get error if the bitmap
    size grow to about 75MB. He is using VS3520 with 16MB momory, 24
    planes.
    
    His program is like this:
    	for (k=0; k<100; k++)
    	   for (l=0; l<12; l++)
    	      bitmap=XCreateBitmapFromData(mydisp,window,buffer,360,480)
    	.
    	.
    error at k=36,l=12
    error message:
    	XIO: fatal IO error 65535 on X server "TPACT4::0.0" after 2401
    	requests(2392 known processed) with 7 events remaining.
    	5XLIB-F-IOERROR, Xlib io error
    
    Is there any limitation when create bitmap?
    
    Thanks.
    
    Johnny
T.RTitleUserPersonal
Name
DateLines
3296.1OXNARD::KLEEKen LeeTue Sep 04 1990 17:276
    Yes, there is a limit.  Your X server must have at least enough virtual
    memory available to hold all the bitmaps you create.  You should get a
    BadAlloc error, rather than an IO-error, though.
    
    Ken
    
3296.2How to extend virtual memory for X server?TPOVC::JOHNNYHOTue Sep 04 1990 23:4414
    Thanks, Ken.
    
    How do I extend the virtual memory for X Server? This is the critical
    issue for customer! Actually, they are developing their mapping
    software on DECwindows. The map they intend to handel with consists of
    hundreds of files each repesents a portion of the big map. The total
    size of the big map is as large as 160MB!
    
    Maybe this is a very common question/problem for imaging software
    developer -- "how do I handle a very large image on DECwindows?"
    
    Could anyone give me some hints or guide lines?
    
    Johnny
3296.3only load what you can useTOOLEY::B_WACKERWed Sep 05 1990 12:227
You shouldn't load any more into the server than you can use at one 
time.  Probably what you need to do is reuse pixmaps.  If you keep the 
total size low then you'll also eliminate paging from display to 
virtual memory and have much better performance.  I don't think 
increasing server memory to over 160M is a very good solution.

Bruce
3296.4Keep most of the map on the clientVINO::MCARLETONReality; what a concept!Wed Sep 05 1990 12:2712
    Since the X Server could be on a remote node that does not support
    virtual memory, it would be best if you could code the application so
    that most of the map is stored in client memory.  You can then copy the
    currently displayed portion to server as needed, keeping the load on
    the server small.

    To do this you would use an XImage data structure on the client and
    a XPutImage call to place the image in a window or pixmap on the server
    screen.

    						MJC
3296.5adjust virtual memory size automatically?TPOVC::JOHNNYHOThu Sep 06 1990 00:105
    Thanks, folks,
    
    If customer upgrade from 16 MB to 32 MB memory, will X server adjust
    its virtual memory size automatically according to size of the system
    memory? or shoud they modify some pa
3296.6JAMMER::JACKMarty JackThu Sep 06 1990 11:052
    Generally yes, but you should always run an AUTOGEN after a hardware
    configuration change.