Weird error when dealing with Clock and Time

[ggggggggggggggg]

When the value of shoot speed is assigned to 0 - 3, the program exits without an error. However, with a value more than 3, this lovely error comes up - "Unhandled exception at 0x770015de in Practice  SFML.exe: 0xC0000005: Access violation reading location 0xfeeefef6."

Here's the two functions that use these variables.

Turent::Init-

void Turent::Init()
{
        sprite.setPosition(400, 300);
        sprite.setTexture(textureManager.turent);
        sprite.setOrigin(sprite.getGlobalBounds().width / 2, sprite.getGlobalBounds().height / 2);
        InScreen.setSize(sf::Vector2f(1024, 768));
        shootSpeed = sf::milliseconds(100); //line where I change the value
}

Turent::Shoot-

void Turent::Shoot(sf::RenderWindow& Window)
{
        if(shootClock.getElapsedTime().asSeconds() > shootSpeed.asSeconds() && sf::Mouse::isButtonPressed(sf::Mouse::Left)) //line where it's used
        {
                Bullet blt;
                blt.Setup(sprite.getPosition().x, sprite.getPosition().y, rotation + 90, sf::Mouse::getPosition(Window).x, sf::Mouse::getPosition(Window).y);
                bullets.push_back(blt);
                shootClock.restart();
        }
}
 

Note these were working perfectly until it stopped.

[Laurent]

You're accessing freed memory. That's all I can say, so use your debugger to find out more.

[ggggggggggggggg]

I don't see how. In my header file I have

sf::Clock shootClock;

and in my .cpp file I have

if(shootClock.getElapsedTime().asSeconds() > 1 && sf::Mouse::isButtonPressed(sf::Mouse::Left))
        {
                Bullet bullet;
                bullet.Setup(sprite.getPosition().x, sprite.getPosition().y, rotation + 90, sf::Mouse::getPosition(Window).x, sf::Mouse::getPosition(Window).y);
                bullets.push_back(bullet);
                shootClock.restart();
        }

It only gives an error with this

shootClock.getElapsedTime().asSeconds() > 1

When I comment it out the turent shoots super fast but it shuts down right.

[Laurent]

I don't see how

That's why debuggers exist...

[ggggggggggggggg]

Right. Ok, thanks.

[ggggggggggggggg]

So I found out why.. I guess. I don't see how this would be even related, but I guess it was.

In my main I had an FPS counter.. For some reason it only gave an error when another clock in another file was used.. Is that normal? They didn't touch each other at all.

[Laurent]

Seriously, what's wrong with the debugger? It will show you exactly where the application crashes. Don't waste your time like this.