Here are a few simple steps that can help resolve the 142-byte memory allocation error issue.

[“Business Unit”:”Code”:”BU054″,”Label”:”Systems with/TPS”,”Product”:”Code”:”SSEQ5Y”,”Label”:”Personal Communication”,”Platform ” :[“code”:”PF025″,”label”:”Platform Independent”],”Version”:”5.9″,”Industry”:”code”:”LOB35″,”label”:”Mainframe SW” ]

APAR Status

  • Closed Despite Error.

  • Error Description

  • Personal Communications 5.9.2 on Windows XP SP3When trying to start a PCOMM session The client may receive the message PCSERR100- "Failed to match66050 bytes of Windows Global Memory HeapPlease close one or more Windows information applications and try again."
  • Local Solution

  • Short Description Of The Problem

    What’s the meaning of this error memory allocation failed?

    Re: What the single error means? MemoryError: Failed to allocate memory, definition 964 bytes Es? only limited storage space is available. Due to fragmentation, or simply because there is a lot to allocate, everything has reached its limit and can no longer allocate.




  • ************************************************** ****** *** *************************** APPLICABLE USERS: All Drivers *********************** ******************************************************** ***** ****PROBLEM DESCRIPTION: Intermittent context word PCSERR100** PCOMM sessions that start immediately ************************** ******************************************************** ***** **** RECOMMENDATION : ******************************************************** ******************************When working with PCOMM sessions, users receivePop-up PCSERR100 logo and need to restart running serveragain with PCOMM.
  • Closing The Issue

  • When PCSWLIB.DLL allocates memory, calls MapViewofFileEx.block of virtual addresses. The whole block must be free of thisbe for close to the point of attribution. Working no code shouldcheck the availability of this block of memory. inCode changes introduce thischeck by saying On Propertystay tied to "About Block Program".Fix PCOM 5.9.6.0 production update
  • Workaround

  • Comments



  • APAR Information

  • APAR Is Wrapped By One Or More Of The Following Elements:

  • APAR Has Been Redirected To One Or More System Routes With The Following:

  • Modules/Macros

  • PCSWLIB
  • Correct Information

  • Fixed PCOMM Component Name

    error allocating 142 bytes of memory

    Combo V5

  • Fixed Identifier

    5639I7000

  • Applicable Component Component Levels

  • R590 PSY IP23069

    UP09/12/22 I 1000

  • APAR Number

    IC64204

  • Name Of The Reported PCOMM Component

    Combo V5

  • ID Of The Specified Component

    5639I700J

  • Reported Version

    590

  • Status

    CLOSED

  • EP

    No

  • ABOVE

    How to fix the’couldn’t allocate memory’error?

    I have the same specific “Could not allocate memory” error, which occurs in two cases. Just check the disk usage with the top command to see if all the ram/swap is being done. Also check the generated disk usage with the df command. B. df -kh so that your build disk can be written as full

    Not HIPER

  • Special Attention

    Don’t show

  • Date Posted

    28.10.2009

  • Closing Date

    2009-11-02

  • Last DateChanges

    22/12.Aria-expanded=”true”>

  • Sue Kelling

    unread,

    20 January 1999 20 09:00:00 January 1999

    in

    We received several computers running NT windows 4.0. Blend a is installed on these computers

    Installed

    SP3 and SP4 packages. .We .get .the following .error .message

    error allocating 142 bytes of memory

    if .we .try to .open more than .several .or .5 .emulator .windows:

    PCSERR100 .2 .. Failed to allocate xxxx bytes from the Windows global memory heap. Close one or more Windows applications and try again
    .

    On these machines, memory is far from exhausted, and
    pagefile.sys will close if you simply have a lot of memory available. I tried to push
    the Windows Shared Desktop heap through the entire registry
    as described in the tech manual from Microsoft. This didn’t seem to help
    fix the problem, it just increased the number of bytes that
    definitely could not be selected. Try

    What else can I do to fix this?

    Thank you,
    Sue Kelling
    kel…@us.ibm.com