Bug 676863

Did you start chrome while sitting in this directory?  Where you looking at content in this directory with chrome?  chrome and firefox for that matter leak lots of open file descriptors so this could be a leak from chrome to the sandbox but I seldom if ever have seen a leak of a link file descriptor.

nope, negative at both questions ... i start chrome from the menu and i have no idea what working directory have the applications started this way ...
and none of the terminal used had been in that directory ..  it is happening regardless of the state (logout form kde, login again, starting chrome and watch as AVC selinux message appear telling me about what happened)

What does printenv | grep clhep show?

Also anything in .bashrc or .bash_profile?

(In reply to comment #4)
> Also anything in .bashrc or .bash_profile?

Well, of course shows a lot! clhep have the bin and libs directories in PATH and in LD_LIBRARY_PATH

.basrc script for clhep:

adrian@sev: ~ $ cat /home/physics-tools/env/clhep_scr 
##
## CLHEP ##
##

export CLHEP_BASE_DIR=${tools}/clhep/clhep

export CLHEP_INCLUDE_DIR=${CLHEP_BASE_DIR}/include
export CLHEP_LIB_DIR=${CLHEP_BASE_DIR}/lib

export PATH=$PATH:${CLHEP_BASE_DIR}/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${CLHEP_LIB_DIR}

export C_INCLUDE_PATH=$C_INCLUDE_PATH:${CLHEP_INCLUDE_DIR}
export CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:${CLHEP_INCLUDE_DIR}

but what is connection with chrome???

just for reference i will put here and relevant printenv output:

adrian@sev: ~ $ printenv | grep clhep     
CLHEP_LIB_DIR=/home/physics-tools/clhep/clhep/lib
CPLUS_INCLUDE_PATH=/home/physics-tools/PYTHIA8/include::/home/physics-tools/clhep/clhep/include:/home/physics-tools/geant4/include/:/home/physics-tools/root/root/include:/home/physics-tools/alice/aliroot/include
LD_LIBRARY_PATH=/home/physics-tools/PYTHIA8/lib:/lib:/usr/lib:/usr/local/lib:/usr/X11R6/lib:/lib:/usr/lib:/usr/local/lib:/usr/X11R6/lib:/usr/java/default/jre/lib:/usr/lib64/qt-3.3/lib:/home/adrian/ahome/lib:/home/physics-tools/clhep/clhep/lib:/home/physics-tools/geant4/lib/Linux-g++:/home/physics-tools/clhep/clhep/lib:/lib:/home/physics-tools/geant4/lib/Linux-g++:/home/physics-tools/alien/api/lib:/home/physics-tools/alien/globus/lib:/home/physics-tools/root/root/lib:/home/physics-tools/alice/aliroot/lib/tgt_linuxx8664gcc:/home/physics-tools/alice/geant3/lib/tgt_linuxx8664gcc
PATH=/home/physics-tools/PYTHIA8/bin:/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/X11R6/bin:/usr/java/default/jre/bin:/usr/lib64/qt-3.3/bin:.:/home/adrian/ahome/bin:/home/physics-tools/clhep/clhep/bin:/home/adrian/geant4/bin/Linux-g++:/home/physics-tools/alien/api/bin:/home/physics-tools/alien/globus/bin:/home/physics-tools/root/root/bin:/bin:/home/physics-tools/alice/aliroot/bin/tgt_linuxx8664gcc
C_INCLUDE_PATH=/home/physics-tools/PYTHIA8/include::/home/physics-tools/clhep/clhep/include:/home/physics-tools/geant4/include/:/home/physics-tools/root/root/include:/home/physics-tools/alice/aliroot/include
CLHEP_BASE_DIR=/home/physics-tools/clhep/clhep
CLHEP_INCLUDE_DIR=/home/physics-tools/clhep/clhep/include

Thanks for looking into it!
Adrian

If it is in your LD_LIBRARY_PATH, then the dynamic linker will try to search it when starting up any dynamically linked executable, including chrome.  Just dontaudit it.

ok, mystery solved! i will add the proper se policy.
Thanks!!