OAuth login requires authorization over and over again

Summary

Gitlab oauth login requires authorization of the application over and over again though nothing has changed.

Steps to reproduce

Any web application that requires oauth seems to work. Just use it, log in into gitlab, authorize the application and wait one or two days to be sure. Sometimes it happens even twice a day. I have to re-authorize the application even if my gitlab session is still valid (i.e. when starting my application and it redirects me to gitlab I do not have to enter my username/password but still have to confirm that my application is authorized)

Example Project

I think any project using oauth will suffice to yield this behaviour.

What is the current bug behavior?

About once or twice a day I have to authorize my application. As you can see in the "applications" tab in my user settings I have 224 authorized applications though actually there are only 3. And the application itself has 259 authorized clients which is basically all me. Things go really wrong here. (see screenshots). I've tested several settings (still logged in vs. gitlab session expired, remember me yes/no, used browser vs. private mode, nothing seems to make a difference)

What is the expected correct behavior?

I would expect the same authorization behaviour with gitlab as for example with google or dropbox oauth which is that once I authorized an application I will never ever get asked again until I manually revoke that authorization. I would expect the number of clients shown in my settings to reflect the actual number of clients. I would expect the number of authorized applications to be the same as the number of displayed applications in the list below (3 in my case).

Relevant logs and/or screenshots

Output of checks

GitLab Enterprise Edition 9.4.1-ee 1ae00127

Results of GitLab environment info

Results of GitLab application Check

I will hand in those informations later as soon as our admins provided them to me.