Strange bug with FPS counter, popping up in QB64

[catclaw]

Hi!
Sorry, I couldn't find a way to post this in "Bugs"-section, but here we go...

I'm a mostly daily user of QB64 as it was chosen as the standard programming language where I work (https://www.spacechain.org/download/download.html ) , and I was coding yesterday, just as today - nothing have changed. I haven't installed any new programs or done any reconfiguration, or anything at all.
I was coding yesterday - I shutdown my computer, and then I woke up, made my tea while the computer was booting, and then I started QB64 to start writing - but suddenly, this overlay OSD FPS-counter shows up after just a few seconds.
I thought at first that I had activated some kind of debug function and I've tried every key-combination I can think of, looked through the menus (as much as that can be seen, as it's below the FPS-counter.) but couldn't disable it.
I've tried to restart several times, even the computer too, but it keeps coming back.
The last thing I need right now, is to re-install QB64, because of lot reasons, like post-modifications of the compiler that I've no idea of, but the guy who instructed me on how-to, and I can't find that e-mail.
I can't just e-mail him and wait a couple of days before he answers, as I've got tons of work to do and I can't sit around doing nothing for days in the office.
So please! Help! I'm really stuck here.

Thanks in advance.
With regards.

[SMcNeill]

I can’t think of *anything* in QB64 which could possibly produce those results for you.  For starters, the IDE is a simple SCREEN 0 text screen.  It can’t do overlays.

I’m thinking some gaming software, or OS monitoring software is running in the background.  If it’s still there after rebooting, check your Startup program list and see what might’ve changed or been added recently to give your windows a FPS counter.

[catclaw]

Ok?!! Thanks for the answer.
So.. For real? Because I haven't touched my computer between yesterday and today!!
Hmmm… Let's do as you propose and see if I find anything in boot or so. (I've tried re-booting, several times actually - it didn't help.)

It's just got even more stranger.

[Petr]

Try use MSCONFIG for see what is run after start, this maybe it is something with graphic card setings or with graphic card drivers or some Windows program for windows 'boost'.

[TempodiBasic]

Hi Catclaw

to be more specific...

what version of QB64 (take info from Help menu) do you use?
what Os do you use?
What kind of software can do this measures?

[catclaw]

Hey guys!

I really tried everything, re-installed the GPU drivers several times, reset all configs (I've got many screens… See pic…) - even checked/unchecked stuff in the boot systematically (really time-consuming task) - but nope.
However, I downloaded QB64 again, and extracted it in a temp directory, and then copied and replaced the qb64.exe file only, in the real installation folder, and - tada!
It is gone!

Both versions were the latest build, to answer TempodiBasic's question.
The OS is Windows 10, and well - a lot of software out there can do this, but I noticed that the file-size of the two qb64.exe files were different by a couple of hundreds of kb's.
I think the old version was infected by some malware or spyware, and I or something in the QB64-code accidentally activated its built-in debug-function - because it also showed CPU and cores temperature among other things.
I've used SpyBot Search and Destroy (recommended) to scan my C: drive and it found a handful of crap, which it deleted.
The other two drives are 8 TB each, and it would take days to scan - so I skipped them.

However, it might be a good idea to add some simple CRC-check to qb64.exe, just to be on the safe side.
I'm gonna do that from now on with my own programs...

[FellippeHeitor]

I or something in the QB64-code accidentally activated its built-in debug-function - because it also showed CPU and cores temperature among other things.

This "built-in debug-function" that "also showed CPU and cores temperature among other things" simply doesn't exist in QB64. Your version sure got infected locally.

Glad you've sorted it out.

[catclaw]

This "built-in debug-function" that "also showed CPU and cores temperature among other things" simply doesn't exist in QB64. Your version sure got infected locally.

Glad you've sorted it out.

I think so too, as the file sizes were different.
That's why I'm suggesting some kind of CRC-check when qb64.exe starts, to make sure it's not compromised.