Posts: 2,545
Threads: 255
Joined: Apr 2022
Reputation:
133
Anyone have a handle on what is messing up the ASCII display? In SCREEN 0, solid lines are dashed lines and ASCII characters like 254 do not display properly. I also noted the font irregularities previously mentioned, but in the created exe projects, not just the IDE. Something is certainly off in this release.
Pete
Posts: 1,191
Threads: 113
Joined: Apr 2022
Reputation:
102
I just had something strange happen. Code that was running normally for me suddenly started crashing. Loading different code in did the same thing. According to Task Manager the QB64PE IDE (v 3.12.0) was using over 256MB of RAM while sitting idle. Closing and then reopening the IDE corrected the issues with the IDE using around 86MB which is what I would expect.
I normally leave the IDE running for days (heck sometimes weeks) at a time and have never run into this before.
I'm watching the RAM usage right now for the IDE continuing to climb after the restart (which is normal). It seems to have settled down now at 87,084K.
I'll keep mindful of what I'm doing if the issue happens again to help give some clue as to why this would have happened?
Has anyone else seen high RAM usage coming from their IDE?
New to QB64pe? Visit the QB64 tutorial to get started.
QB64 Tutorial
Posts: 4,132
Threads: 187
Joined: Apr 2022
Reputation:
250
Terry are you still using Windows 7 or into Linux now?
b = b + ...
Posts: 2,545
Threads: 255
Joined: Apr 2022
Reputation:
133
I'm pretty sure Terry is still running Windows 3.1 on a laboratory squirrel. The poor little critter probably spun clean out of its wheel.
Pete
Shoot first and shoot people who ask questions, later.
Posts: 2,905
Threads: 341
Joined: Apr 2022
Reputation:
264
@Pete You're gettold and need to take your memory-enhancing drugs again. Win 3.1 would *NEVER* boot up; it wasn't an OS. It ran under DOS.