IBM Support

IZ65166: DETACHED THREADS NOT GETTING TERMINATED DUE TO INCONSISTENCY APPLIES TO AIX 5300-12

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After the creation of the threads, all the threads are
    set as detached.During the termination,there are
    few threads which shows its state as joinable and are not
    getting completely cleaned up.
    
    The threads marked as detached are getting modified as
    joinable.
    

Local fix

  • Workaround:
    Create the thread in detached state, instead of setting
    the state later using the pthread_detach() routine.
    

Problem summary

  • The detached threads in threaded application will turn to
    zombie thread and the application will eventually run out of
    memory.
    

Problem conclusion

  • The detached flag was getting lost because of synchronization
    issues. Fixed the same to resolve this issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ65166

  • Reported component name

    AIX 5.3

  • Reported component ID

    5765G0300

  • Reported release

    530

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Submitted date

    2009-11-13

  • Closed date

    2009-11-13

  • Last modified date

    2013-03-28

  • APAR is sysrouted FROM one or more of the following:

    IZ59591

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    AIX 5.3

  • Fixed component ID

    5765G0300

Applicable component levels

  • R530 PSY U835230

       UP10/04/15 I 1000

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11P","label":"APARs - AIX 5.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"530","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 March 2013