Slow rendering #34
Labels
No Label
C
Category/Applications
Category/Drivers
Category/General
Category/Kernel
Category/Libraries
Eolite
FASM
FS
HLL
Influence/Settings
Influence/Text/TYPO
IRCC
Kernel
Kind
Breaking
Kind
Bug
Kind
Build
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: KolibriOS/kolibrios#34
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After some time while working, suddenly drawing each frame (we do not take into account the cursor) takes 13:1.5 seconds. Although up to this point everything is smooth. The problem is solved by a banal reboot, but after a while it resumes. At the same time, this thing consumes 50% of the processor. GT 430 video card. AMD Athlon II X3 450 processor.
And why does the Doom game eat 100% of the CPU? (This is not that important, but I want an answer)
KOPbI4
Can it be reproduced in QEMU? If yes, what options are used?
dunkaist
I haven’t tried to reproduce it in QEMU, and it’s unlikely that I’ll succeed (I haven’t worked with it much). It only worked on a real computer. Most likely, this is the fault of the hardware, because on my friend’s computer everything was stable (the performance is about the same, his is even a little weaker. If necessary, he has an Intel processor, I don’t know more detailed characteristics. The video card is also NVIDIA.)
KOPbI4
Unfortunately, I can't reproduce the issue to investigate it.
If you manage to reproduce it in an emulator (say, QEMU), there might be a chance to debug it.
dunkaist
I will try to find a way to reproduce this problem in QEMU.
Do you think this could be somehow influenced by the fact that my processor has 3 cores (1 core is blocked by the manufacturer due to low stability)? Although my friend, whom I tested, had 2 cores (there were no errors)... If there are any more clues, I’ll tell you
KOPbI4
Currently KolibriOS uses only one CPU core. 3 cores shouldn't cause the issue.
dunkaist
It turned out that the bug was floating... It hasn't appeared again yet
KOPbI4