[Windows XP and 7] Crash on exit

• Aug 27, 2014 - 19:10
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

MuseScore 2 beta1, Windows XP

Reproduce:
1. Open MuseScore
2. Close MuseScore

Expected result: MuseScore closes.
Actual result: crash. It is a standard Windows message "Memory could not be read".

Screenshot: crash

Attachment Size
musescore_after_exit_winxp.JPG 16.51 KB

Comments

• Aug 27, 2014 - 19:54
Title Crash on exit in Windows XP ⇒ Crash on exit in Windows XP, 7

MuseScore 2 beta1, Windows 7.
Same crash on exit, but only in a few cases.

I use PortAudio driver. I do not have a crash when using "ASIO" API, otherwise getting a crash.
Screenshot: prefs

Crash screenshot:
crash
Full log from this window (translated to English):

Problem signature:
  Name of problem event:	APPCRASH
  Application name:	mscore.exe
  Application version:	0.0.0.0
  Application timestamp:	0b307fa0
  Name of the module with error:	rig3asio32.dll
  Version of the module with error:	3.0.0.625
  Timestamp of the module with error:	4da2fc1a
  Exception code:	c0000005
  Exception offset:	00048706
  OS version:	6.1.7601.2.1.0.256.1
  Language code:	1049
  Additional information 1:	0a9e
  Additional information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional information 3:	0a9e
  Additional information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0419

If the privacy statement on the Internet is not available, check with its local version:
  C:\Windows\system32\ru-RU\erofflps.txt
Attachment Size
musescore_crash_win7.png 21.1 KB
musescore_preferences2.png 32.59 KB

Reply

• Dec 2, 2014 - 10:47
Status (old) active ⇒ closed

MuseScore 1.3 crashes too.

Uninstall this software and MuseScore should close nicely.

Yes, after uninstalling

  • Native Instruments Rig Control 3
  • Native Instruments Session Control
  • Native Instruments Mobile I/O

there are no crashes in MuseScore 1.3 and MuseScore 2 nightly 4934cf0 (December 2nd, 2014).

Reply