[jira] [Commented] (TS-2047) RamCacheCLFUSCompressor scheduled before RamCacheCLFUS initialization can cause seg fault if compressor runs before RamCacheCLFUS::init

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712742#comment-13712742 ] 

ASF subversion and git services commented on TS-2047:
-----------------------------------------------------

Commit ea560cecc53c0c2563e3baf76a8d0fd2420ae953 in branch refs/heads/master from [~psudaemon]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ea560ce ]

TS-2047: Schedule RamCacheCLFUSCompressor in RamCacheCLFUS::init instead
of immediatly after instantiation.

                
> RamCacheCLFUSCompressor scheduled before RamCacheCLFUS initialization can cause seg fault if compressor runs before RamCacheCLFUS::init
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TS-2047
>                 URL: https://issues.apache.org/jira/browse/TS-2047
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Phil Sorber
>
> The RamCacheCLFUSCompressor is scheduled in the new_RamCacheCLFUS function instead of the init. If Vol init (and subsequently RamCacheCLFUS::init) takes too long the compressor may run before a vol is assigned to the RamCache and causes a segfault.
> I was able to reproduce this with --enable-debug and 18 volumes. This delayed the RamCache init long enough for this to hit.
> This may be the cause of TS-1612 as well, but it isn't clear from that bug report.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira