T.R | Title | User | Personal Name | Date | Lines |
---|
1993.1 | | XANADU::jerryc.zko.dec.com::tamara::Cummings | Jerry Cummings, TeamLinks | Mon Feb 17 1997 09:46 | 9 |
| In general it means the user's PC is running low
on resources; memory, window handles, device contexts,
etc.
Does it happen on those PC's if freshly booted and
with no programs in the startup group?
Jerry
|
1993.2 | After reboot fine for some time .. | TAV02::CHAIM | Semper ubi Sub ubi ..... | Tue Feb 18 1997 01:45 | 12 |
| >
>Does it happen on those PC's if freshly booted and
>with no programs in the startup group?
>
No, it appears to be an accumalitive type of problem; after a fresh reboot it
will work fine for some time (several hours according to the customer) and then
will stop working. On other PCs it works fine even after long use.
Thanks,
Cb.
|
1993.3 | | XANADU::jerryc.zko.dec.com::tamara::Cummings | Jerry Cummings, TeamLinks | Tue Feb 18 1997 11:00 | 18 |
| Then we need to start poking around at what the
differences are. First of all, it might not be
TeamLinks that's the resource leak. Are the problem
PCs running and actively using software that the
non-problem PCs are not?
What's different between the PCs in terms of software,
printers, video, etc.
Do the users of the PCs do different things with
mail, receive different types of attachments, etc.
Maybe run a resource meter and watch for drops in
resources that recover when you'd expect that they
might.
Jerry
|