Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ames!fxgrp!mikew From: mikew@fx.com (Mike Wexler) Newsgroups: comp.windows.x Subject: Re: resource ID allocation Message-ID: <1991Feb20.211200.137@fxgrp.fx.com> Date: 20 Feb 91 21:12:00 GMT References: Sender: news@fxgrp.fx.com Reply-To: mikew@fx.com Distribution: comp Organization: FXD/Telerate, Mountain View, CA Lines: 21 harkcom@spinach.pa.yokogawa.co.jp writes: >The reults of my little sorti were: > The allocation of resource ID's is handled by Xlib and there > is no mechanism for reusing used ID's. One can easily > be constructed though... > The idea that a client could use up all of the valid ID's > is pretty far-fetched. A client would have to be run > continuosly for an awfully long time to use them all up. I have actually seen this happen on a real application under a very heavy workload. The application basically displays error messages. When a new one comes in it blinks (changes the background color back and forth). Because this was a Motif/Xt based program and at least one of the two colors used for blinking wasn't used by another widget, whenever the application blinked, it would use up a resource id. The application would fail after a few days of receiving messages constantly (fast enough so that the blink was continuous). -- Mike Wexler (mikew@fx.com)