Directory changes after opening certain files - vim

Question

EDIT
The scenario changed. Sorry, for posting question a bit too early.
When opening a file (vim filename.ext, or :e filename.txt, etc.), when the CWD is ~/Sites/A, vim changes to another CWD (~/Sites/B).
I found out, that vim does this because of a file in my ~/.vim/view/ folder, called ~=+Sites=+B=+src=+filename.txt=.
The file inside ~/.vim/view/ contains:
let s:so_save = &so | let s:siso_save = &siso | set so=0 siso=0
argglobal
setlocal fdm=manual
setlocal fde=0
setlocal fmr={{{,}}}
setlocal fdi=#
setlocal fdl=0
setlocal fml=1
setlocal fdn=20
setlocal fen
silent! normal! zE
let s:l = 200 - ((13 * winheight(0) + 11) / 23)
if s:l < 1 | let s:l = 1 | endif
exe s:l
normal! zt
200
normal! 030|
lcd ~/Sites/B
let &so = s:so_save | let &siso = s:siso_save
doautoall SessionLoadPost
" vim: set ft=vim :
Why is the line lcs ~/Sites/B standing in this file? Inside ~/Sites/B never existed a file called filename.ext.
For the sake of completeness, this is my question, before I localized the error:
When i vimgrep something in a codebase located in ~/Sites/a (e.g. :vimgrep DateCell src/**/*) vim's current working directory changes to another directory ~/Sites/B.
Every subsequent call to vimgrep or another working-directory-aware-command fails or returns wrong results, because it is operating in the ~/Sites/B directory.
What could cause this?
What I do, to achieve the error / wrong behaviour:
cd ~/Sites/A
vim
vimgrep something src/**/*
:!pwd shows ~/Sites/B
:quit
pwd shows ~/Sites/A
EDIT
It turns out, that the directory change also happens if I don't use vimgrep. I still don't know what produces the error.
BTW: It is always the same directory (~/Sites/B), vim changes to. No matter in which directory i am working.
Vim Version: 8.0.2
OS Version: OS X 10.10.5

Answer 1

The ~=+Sites=+B=+src=+filename.txt= is a saved view for ~/Sites/B/src/filename.txt. The question is: Why does it get loaded when you open a file (with the same name, or any, not entirely clear from your question) from another directory?
Normally, views have to be created and restored manually. You seem to have something in your configuration (:autocmd) that automatically restores saved views, and that something has a bug in its path lookup (or, less likely, your filesystem is messed up and you have symlinks there). Find that, and turn it off / fix it.