Emulator Issues #11718

QT: Rapid screenshots freeze or crash

Added by ryanebola16 almost 2 years ago. Updated over 1 year ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

Super Smash Bros. Brawl

Game ID? (right click the game in the game list, Properties, Info tab)


MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

WIIScrubber edited ISO, only replaces music and intro video. Works fine on Dolphin and real Wii.

What's the problem? Describe what went wrong.

Rapid screenshots freeze or crash Dolphin. This issue did not occur in WX.

What steps will reproduce the problem?

  1. Proceed to Brawl's Brawl mode character select screen
  2. Press the screenshot hotkey as rapidly as possible
  3. Dolphin should freeze or crash within ~20 screenshots

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

Yes, 10153

Is the issue present in the latest stable version?

No, 5.0

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool and anyone who is building Dolphin on their own can use git bisect.)


What are your PC specifications? (CPU, GPU, Operating System, more)

Win 10 Pro x64
Intel Core i7-4702MQ CPU @2.20GHz
GeForce GT 750M
2x 8GB Hynix 1600MHz
GeForce Game Ready Driver 425.31


#1 Updated by JMC4789 almost 2 years ago

Does it happen in single core?

#2 Updated by ryanebola16 almost 2 years ago

Yes, occurred in both single and dual core.

#3 Updated by ryanebola16 almost 2 years ago

Also appears to be independent of ubershader settings

#4 Updated by JMC4789 almost 2 years ago

  • Assignee set to spycrab0
  • Status changed from New to Accepted

Appears to be a Qt regression.

#5 Updated by JMC4789 almost 2 years ago

Technically it won't happen in latest master... unless you enable the debug GUI.

#6 Updated by JosJuice almost 2 years ago

  • Regression changed from No to Yes
  • Milestone set to Current

Also happens when holding the frame advance key. Like JMC just mentioned, 5.0-10607 makes it so that it only happens if you have the debugger enabled, but this isn't a proper fix for the issue.

Dolphin doesn't necessarily always freeze or crash from the testing I've done, but the GUI gets unresponsive due to the large number of backlogged EmulationStateChanged events, and sooner or later you usually get an "Unable to resolve read address" panic alert with the following stack trace:

    [External Code] 
    Dolphin.exe!QtMsgAlertHandler::__l2::<lambda>() Line 67 C++
    Dolphin.exe!RunOnObject<bool <lambda>(void) >(QObject * object, QtMsgAlertHandler::__l2::bool <lambda>(void) && functor) Line 34    C++
    Dolphin.exe!QtMsgAlertHandler(const char * caption, const char * text, bool yes_no, Common::MsgType style) Line 75  C++
    Dolphin.exe!Common::MsgAlert(bool yes_no, Common::MsgType style, const char * format, ...) Line 129 C++
    Dolphin.exe!PowerPC::ReadFromHardware<0,unsigned int,0>(unsigned int em_address) Line 255   C++
    Dolphin.exe!Dolphin_Debugger::WalkTheStack(const std::function<void __cdecl(unsigned int)> & stack_step) Line 56    C++
    Dolphin.exe!Dolphin_Debugger::GetCallstack(std::vector<Dolphin_Debugger::CallstackEntry,std::allocator<Dolphin_Debugger::CallstackEntry> > & output) Line 89    C++
    Dolphin.exe!CodeWidget::UpdateCallstack() Line 293  C++
    Dolphin.exe!CodeWidget::Update() Line 272   C++
    [External Code] 
    Dolphin.exe!Settings::EmulationStateChanged(Core::State _t1) Line 514   C++
    [External Code] 
    Dolphin.exe!main(int argc, char * * argv) Line 220  C++
    Dolphin.exe!WinMain(HINSTANCE__ * __formal, HINSTANCE__ * __formal, char * __formal, int __formal) Line 104 C++
    [External Code] 

#7 Updated by JosJuice over 1 year ago

Actually, the screenshot situation does not seem to be improved much by 5.0-10607. I was assuming it was similar to the frame advance situation and didn't actually test the screenshot situation.

#8 Updated by JosJuice over 1 year ago

  • Status changed from Accepted to Fix pending

#9 Updated by JosJuice over 1 year ago

  • Status changed from Fix pending to Questionable

The PR fixes the issue for me but not the issue reporter, so... Let's mark it as questionable for now, I guess?

#10 Updated by ryanebola16 over 1 year ago

Checked again for good measure. Reproduced in 5.0-11274.
And a link to the crash dump:

Also available in: Atom PDF