Project

General

Profile

Emulator Issues #11560

Multiple OSReport calls from the game lag Dolphin

Added by UnclePunch 14 days ago. Updated 13 days ago.

Status:
New
Priority:
Normal
Assignee:
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

What's the problem? Describe what went wrong.

Multiple OSReport calls from the game lag Dolphin. This issue was not present before the Qt UI change.

What steps will reproduce the problem?

Use this gecko code with Melee v1.02

$OSReport Heap Space
C21A4E88 0000000E
806DA760 3D808034
618C4168 7D8903A6
4E800421 7C641B78
4800002D 7C6802A6
3DC08034 61CE56A8
7DC903A6 4E800421
48000034 4E800021
42820000 C40F4000
3D3851EC 4E800021
52656D61 696E6720
48656170 20537061
63653A20 30782558
00000000 887E0020
60000000 00000000

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-9577

Is the issue present in the latest stable version?

No

History

#1 Updated by JMC4789 14 days ago

Have you tried turning off logging to the GUI? Wx had the nasty habit of actually crashing on too many log calls.

#2 Updated by UnclePunch 14 days ago

JMC4789 wrote:

Have you tried turning off logging to the GUI? Wx had the nasty habit of actually crashing on too many log calls.

We actually started our project using Wx (iishiruka) and ported our changes to mainline just recently.

The project is a replay systen, and we have Melee run some ASM to detect if a desync in the replay occurred, and when it does it outputs about 5 OSReports containing info about the desync. Back on Wx, this was handled perfectly, no slowdowns or crashes, all being displayed in the GUI. However, after the code was ported up to mainline, the game began to lag a ton when these OSReports were displayed in the GUI log.

#3 Updated by JMC4789 14 days ago

  • Assignee set to spycrab0

Wx did it asynchronously and could randomly crash while dumping logs. I'm guessing that because Qt actually does it in order that it can lag. I'll ping spycrab anyway. Probably could be optimized maybe.

#4 Updated by JosJuice 13 days ago

Please check whether 5.0-9583 fixed it.

Also available in: Atom PDF