WinXp crash master r5385 and 1.12 r5403 and --developer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Triaged
|
Medium
|
Unassigned |
Bug Description
Mixxx crashes after the Skin is shown.
Daniel Schürmann (daschuer) wrote : | #1 |
Daniel Schürmann (daschuer) wrote : | #2 |
Daniel Schürmann (daschuer) wrote : | #3 |
Debug [Main]: Recordings folder set to "C:/Dokumente und Einstellungen/
Eigene Dateien/Eigene Musik/Mixxx/
Debug [Main]: AnalysisLibrary
Debug [Main]: AnalysisLibrary
Debug [Main]: DlgAnalysis(
Warning [Main]: ControlDoublePr
trol]" , "show_vinylcontrol" )
Warning [Main]: ControlDoublePr
trol]" , "show_vinylcontrol" )
Debug [Main]: MixxxLibraryFea
Debug [Main]: LibraryTableMod
Debug [Main]: WSearchLineEdit
Debug [Controller]: ControllerManager: Setting up devices
Debug [Controller]: Scanning PortMIDI devices:
Debug [Controller]: Found output device # 0 Microsoft MIDI-Mapper
Debug [Main]: Starting LibraryScanner thread.
Debug [Controller]: Found output device # 1 Microsoft GS Wavetable SW Synth
Debug [Controller]: Scanning HSS1394 devices:
Debug [Controller]: Nodes detected: 0
Debug [Controller]: Scanning HID devices:
[New Thread 1056.0x104]
[New Thread 1056.0xf44]
Debug [Main]: SoundManager:
Debug [Controller]: ControllerManag
Debug [Controller]: Controller polling stopped.
gdb: unknown target exception 0xe06d7363 at 0x7c812fd3
Program received signal ?, Unknown signal.
[Switching to Thread 1056.0xf44]
0x7c812fd3 in RaiseException () from C:\WINDOWS\
(gdb) thread backtrace all
No symbol table is loaded. Use the "file" command.
(gdb) bt
#0 0x7c812fd3 in RaiseException () from C:\WINDOWS\
#1 0x00a29339 in MSVCR120!
from C:\WINDOWS\
#2 0x00a6da6a in fcloseall () from C:\WINDOWS\
#3 0x621efe30 in ?? ()
#4 0x006c1f21 in mixxx!?
()
#5 0x02000000 in ?? ()
#6 0x00451818 in mixxx!hid_error ()
#7 0x621efeec in ?? ()
#8 0x67026c70 in QtCore4!
from C:\Programme\
#9 0x0467bc88 in ?? ()
#10 0x00a3c001 in _get_tlsindex () from C:\WINDOWS\
#11 0x0012fb24 in ?? ()
#12 0x7c80b729 in KERNEL32!
from C:\WINDOWS\
#13 0x00000000 in ?? ()
(gdb)
Daniel Schürmann (daschuer) wrote : | #4 |
Debug build:
[New Thread 3908.0xd30]
[New Thread 3908.0xe54]
[New Thread 3908.0x9ac]
[New Thread 3908.0xfb0]
gdb: unknown target exception 0xe06d7363 at 0x7c812fd3
Program received signal ?, Unknown signal.
[Switching to Thread 3908.0x324]
0x7c812fd3 in RaiseException () from C:\WINDOWS\
(gdb) thread backtrace all
No symbol table is loaded. Use the "file" command.
(gdb) bt
#0 0x7c812fd3 in RaiseException () from C:\WINDOWS\
#1 0x00fe0b86 in MSVCR120D!
from C:\Programme\
#2 0x00fec2a1 in MSVCR120D!
from C:\Programme\
#3 0x00fec35d in MSVCR120D!
from C:\Programme\
#4 0x00998f8c in mixxx!hid_exit ()
#5 0x00997024 in mixxx!hid_exit ()
#6 0x00997a99 in mixxx!hid_exit ()
#7 0x009975a1 in mixxx!hid_exit ()
#8 0x00993ece in mixxx!hid_exit ()
#9 0x00549b0b in mixxx!hid_exit ()
#10 0x0054ad8e in mixxx!hid_exit ()
#11 0x00549f5d in mixxx!hid_exit ()
#12 0x00547e30 in mixxx!hid_exit ()
#13 0x00851251 in mixxx!hid_exit ()
#14 0x6707383f in QtCored4!
from C:\Programme\
#15 0x00f23651 in beginthreadex () from C:\Programme\
#16 0x00f23861 in endthreadex () from C:\Programme\
#17 0x7c80b729 in KERNEL32!
from C:\WINDOWS\
#18 0x00000000 in ?? ()
(gdb) bt all
No symbol table is loaded. Use the "file" command.
(gdb)
Daniel Schürmann (daschuer) wrote : | #5 |
The 1.12 branch 5377 is not effected. This is interesting, because the difference it mainly the new soundsource.
But it crashes before Mixxx has the chance to touch a file. And why does the --developer flag makes a difference.
Daniel Schürmann (daschuer) wrote : | #6 |
Why are the backtraces so different. Shomething really bad is going on.
Uwe Klotz (uklotzde-deactivatedaccount) wrote : | #7 |
Did you do a clean rebuild after switching branches? Might help.
I did a quick analysis on Fedora 21 x86_64 with valgrind and the --developer option, but can't spot any warnings related to a SoundSource!?
But what I see are many "Conditional jump or move depends on uninitialised value(s)" warnings for SkinContext:
==19942== Conditional jump or move depends on uninitialised value(s)
==19942== by 0x79AD983: ??? (in /usr/lib64/
==19942== by 0x79B8042: QScriptValue:
==19942== by 0xB470DD: SkinContext:
==19942== by 0xB41275: LegacySkinParse
==19942== by 0xB3EEDF: LegacySkinParse
==19942==
==19942== Conditional jump or move depends on uninitialised value(s)
==19942== by 0x79AD983: ??? (in /usr/lib64/
==19942== by 0x79B8042: QScriptValue:
==19942== by 0xB470DD: SkinContext:
==19942== by 0xB41275: LegacySkinParse
==19942== by 0xB3EEDF: LegacySkinParse
==19942==
==19942== Conditional jump or move depends on uninitialised value(s)
==19942== by 0x79AD983: ??? (in /usr/lib64/
==19942== by 0x79B8042: QScriptValue:
==19942== by 0xB470DD: SkinContext:
==19942== by 0xB41275: LegacySkinParse
==19942== by 0xB3EEDF: LegacySkinParse
==19942==
==19942== Conditional jump or move depends on uninitialised value(s)
==19942== by 0x79AD983: ??? (in /usr/lib64/
==19942== by 0x79B8042: QScriptValue:
==19942== by 0xB470DD: SkinContext:
==19942== by 0xB41275: LegacySkinParse
==19942== by 0xB3EEDF: LegacySkinParse
==19942==
==19942== Use of uninitialised value of size 8
==19942== by 0x79AD983: ??? (in /usr/lib64/
==19942== by 0x79B8042: QScriptValue:
==19942== by 0xB470DD: SkinContext:
==19942== by 0xB41275: LegacySkinParse
Daniel Schürmann (daschuer) wrote : | #8 |
Thank you for the valgrind log. It seams to be some homework open :-/
All binaries are from downloads.
Daniel Schürmann (daschuer) wrote : | #9 |
git5403 is still effected.
Daniel Schürmann (daschuer) wrote : | #10 |
Can one else reproduce the crash?
Daniel Schürmann (daschuer) wrote : | #11 |
I cannot reproduce an a different XP
Daniel Schürmann (daschuer) wrote : | #12 |
Mixxx crashes because of an unhandled C++ exception (0xE06D7363)
http://
Daniel Schürmann (daschuer) wrote : | #13 |
Backtarce of Mixxx 1.12 beta debug git5403 1.12 branch (NOT MASTER)
(gdb) bt
#0 0x7c812fd3 in RaiseException () from C:\WINDOWS\
#1 0x00fd0b86 in MSVCR120D!
from C:\Programme\
#2 0x00fdc2a1 in MSVCR120D!
from C:\Programme\
#3 0x00fdc35d in MSVCR120D!
from C:\Programme\
#4 0x0098e18c in mixxx!hid_exit ()
#5 0x0098c224 in mixxx!hid_exit ()
#6 0x0098cc99 in mixxx!hid_exit ()
#7 0x0098c7a1 in mixxx!hid_exit ()
#8 0x009890ce in mixxx!hid_exit ()
#9 0x0054822b in mixxx!hid_exit ()
#10 0x005492de in mixxx!hid_exit ()
#11 0x0054862d in mixxx!hid_exit ()
#12 0x009488e3 in mixxx!hid_exit ()
#13 0x00947a49 in mixxx!hid_exit ()
#14 0x00947e4f in mixxx!hid_exit ()
#15 0x1000b677 in portaudio!
from C:\Programme\
#16 0x00000000 in ?? ()
Changed in mixxx: | |
importance: | Undecided → Critical |
milestone: | none → 1.12.0 |
summary: |
- WinXp crash git master r5385 + WinXp crash master r5385 and 1.12 r5403 |
RJ Skerry-Ryan (rryan) wrote : Re: WinXp crash master r5385 and 1.12 r5403 | #14 |
If that backtrace is to be believed then this is the only method called:
https:/
which doesn't mention any possibility of throwing.
RJ Skerry-Ryan (rryan) wrote : | #15 |
have you tried the debug diagnostic tool?
http://
that might shed some light
Daniel Schürmann (daschuer) wrote : | #16 |
Tried the Debug And Diagostic Tool but with no success. Do not know what to do.
But I have noticed an other thing Mixxx consumes up to 2 GB Ram before it crashes.
Without --developer it starts much faster, and does not consumes that much memory.
1.12 5377 is not effected
1.12 5387 is not effected
1.12 5403 is effected
master r5385 is effected
I have done two installation cycles to though out random effects.
the first boot up pause happens here:
Debug [Main]: AnalyserWavefor
Debug [Main]: Setting VAMP_PATH to: "C:\Programme\
Debug [Main]: Creating ControllerManager
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Extension ".bulk.xml" total 1 presets
Debug [Main]: Extension ".hid.xml" total 9 presets
Debug [Main]: Extension ".midi.xml" total 85 presets
Debug [Main]: slotSetRateRange 1 0.08
Debug [Main]: slotSetRateRange 1 0.08
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Loading resources from "C:/Programme/
Debug [Main]: Loading resources from "C:/Programme/
-> Here <-
The second one here:
"LibraryScanner 1") "LIBRARY_SCANNER"
Debug [Main]: Requested sample rate: 48000 Hz, latency: 85.3333 ms
Debug [LibraryScanner 1]: DirectoryDAO:
me = "LibraryScanner 1") "LIBRARY_SCANNER"
Debug [Main]: Output channels: 2 | Input channels: 0
Debug [LibraryScanner 1]: LibraryScanner event loop starting.
Debug [Main]: Opening stream with id 6
DirectSound host buffer size frames: 8240, polling period seconds: 0.
r: 48000.000000
InitOutputBuffer() returns 0
Debug [Main]: Opened PortAudio stream successfully... starting
PaHost_
PaHost_StartOutput: IDirectSoundBuf
Debug [Main]: PortAudio: Started stream successfully
Debug [Main]: Actual sample rate: 48000 Hz, latency: 86.3333 ms
-> Here <-
Owen Williams (ywwg) wrote : | #17 |
Try using git bisect to narrow down the exact breaking commit
Daniel Schürmann (daschuer) wrote : | #18 |
I have no Windows build environment. Does anyone else with a windows build environment experience the crash?
Since it happens in master and 1.12 and it started after the fork but there is not much in common and it only happens with the --developers flag ... It could also be also a build server issue.
RJ Skerry-Ryan (rryan) wrote : Re: [Bug 1448630] Re: WinXp crash master r5385 and 1.12 r5403 | #19 |
Do you totally delete c:\Programme\Mixxx each time?
Is it possible that there are some release DLLs left over in there?
On Wed, Apr 29, 2015 at 3:58 PM, Owen Williams <email address hidden> wrote:
> Try using git bisect to narrow down the exact breaking commit
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> WinXp crash master r5385 and 1.12 r5403
>
> To manage notifications about this bug go to:
> https:/
>
RJ Skerry-Ryan (rryan) wrote : | #20 |
The build server 1.12 and master build environments are the exact same
files -- so the only difference between a debug build on master vs 1.12 is
the code.
On Wed, Apr 29, 2015 at 4:20 PM, Daniel Schürmann <
<email address hidden>> wrote:
> I have no Windows build environment. Does anyone else with a windows
> build environment experience the crash?
>
> Since it happens in master and 1.12 and it started after the fork but
> there is not much in common and it only happens with the --developers
> flag ... It could also be also a build server issue.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> WinXp crash master r5385 and 1.12 r5403
>
> To manage notifications about this bug go to:
> https:/
>
Daniel Schürmann (daschuer) wrote : Re: WinXp crash master r5385 and 1.12 r5403 | #21 |
> Do you totally delete c:\Programme\Mixxx each time?
No. I did it just now and installed 1.12 5403 still crashing.
> The build server 1.12 and master build environments are the exact same
files
Maybe a hint. Was the environment changed between 1.12 5387 and 1.12 5403?
Maybe a test would be nice to build 5387 with the current environment.
RJ Skerry-Ryan (rryan) wrote : Re: [Bug 1448630] Re: WinXp crash master r5385 and 1.12 r5403 | #22 |
Hm. No change has happened in the debug environments at all for months.
The only change was that I re-built the release environments. I did this on
2015-04-21 when I sent this message:
http://
On Wed, Apr 29, 2015 at 5:07 PM, Daniel Schürmann <
<email address hidden>> wrote:
> > Do you totally delete c:\Programme\Mixxx each time?
>
> No. I did it just now and installed 1.12 5403 still crashing.
>
> > The build server 1.12 and master build environments are the exact same
> files
>
> Maybe a hint. Was the environment changed between 1.12 5387 and 1.12 5403?
> Maybe a test would be nice to build 5387 with the current environment.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> WinXp crash master r5385 and 1.12 r5403
>
> To manage notifications about this bug go to:
> https:/
>
Daniel Schürmann (daschuer) wrote : Re: WinXp crash master r5385 and 1.12 r5403 | #23 |
Ok, 1.12 5387 is not effected and was build on 24-Apr. So it was already build on the new environment.
On the other hand, the crash started after we have forked 1.12 on both branches and the most recent common commit is
https:/
Autor: RJ Ryan <email address hidden> 2015-04-23 01:26:54
Which is not effected.
So what append? :-/
Do you see any suspicious commit between 1.12 5387 and 1.12 5403?
Can you build a version between them? Maybe we can narrow the error.
Daniel Schürmann (daschuer) wrote : | #24 |
I can reproduce the crash now on my other XP system if I use the same skin like on the other system: Deere.
If I start with on of the other skins, Mixxx does not crash. Swithing to Deere after Mixxx has started works as well.
I have noticed also that LateNight and Deere are eating slowly memory when stated in --developer mode
100 k / s. This does not happen when started without the flag.
Shade is not effected.
Is there an issue with SVG drawings? Maybe Uwes finding (comment #7) is on the right track.
Daniel Schürmann (daschuer) wrote : | #25 |
Good news = Bad news
The crash and the memory leak is gone with 1.12 r5442
Instead I suffer now this:
https:/
Has the bad thing just moved?
This is an indicator of a real bad issue.
Daniel Schürmann (daschuer) wrote : | #26 |
The crash is gone the memory leaking is slowed down with 1.12 r5442
In addition I suffer now this:
https:/
Has the bad thing moved?
This is an indicator of a real bad issue.
There is still a connection: --developer = leak
no developer = not leak.
Can anyone else confirm or not confirm this? We should get a feeling how common this problem is.
Daniel Schürmann (daschuer) wrote : | #27 |
Ok: I have a hint: Now Shade is leaking as well-
I have recently switched to Open Sans.
Still need to verify if this depends?
So fixing Bug #1454649 will fix this?
Daniel Schürmann (daschuer) wrote : | #28 |
No, https:/
This is an older commit
Daniel Schürmann (daschuer) wrote : | #29 |
I have just removed the "font" folder -> no leaking
restored folder -> leaking starts
Daniel Schürmann (daschuer) wrote : | #30 |
The latest issues can also be reproduced on Win10
--developer flag = leaking
shalty (neogeo-dc) wrote : | #31 |
I have been testing r5442 on a w7 x86, and it doesn't leak any of the skins i have tested (late night, deere, shade) with default configuration (except software waveforms because of the usual intel driver opengl crash), with autodj for some hour each, and the --developer option activated, of course.
They all consume between 800-1200, after some time doesn't grow anymore.
Note: about the traces, a process on windows can only use (without special flags on the .exe) 2gb of ram, so when it reaches the limit, can fail almost anywhere. And using valgrind is fine for the majority of the code, but not for #ifdef WIN32 code...
kramer (default-kramer) wrote : | #32 |
On Win7, using the master branch. Specifically, this version: https:/
Problems only happen when using the --developer option. Sometimes I get a crash as soon as the skin shows. Other times it doesn't crash, but waveforms do not show up and almost every track fails to play with this output:
Warning [CachingReaderW
Warning [CachingReaderW
And then it will crash later on. If the VS debugger can be trusted, here is a stack trace of the crashing thread:
atioglxx.
[Frames below may be incorrect and/or missing, no symbols loaded for atioglxx.dll]
> QtOpenGLd4.
0000bc80()
And "arrayIndex" is -1949237504 in this case.
I didn't notice any problems with 1.12, but I didn't use the --developer option often.
Owen Williams (ywwg) wrote : | #33 |
is this still happening? we haven't had reports of straight-up skin crashes in a while
Daniel Schürmann (daschuer) wrote : | #34 |
Yes, the --developer flag leaking still persists.
It was recently reported here https:/
A solution is proposed in
https:/
Changed in mixxx: | |
status: | New → Confirmed |
assignee: | nobody → Daniel Schürmann (daschuer) |
Owen Williams (ywwg) wrote : | #35 |
crashes with --developer are not ideal but not critical. (Could be high, I guess)
summary: |
- WinXp crash master r5385 and 1.12 r5403 + WinXp crash master r5385 and 1.12 r5403 and --developer |
Changed in mixxx: | |
importance: | Critical → Medium |
Changed in mixxx: | |
status: | Confirmed → In Progress |
Changed in mixxx: | |
importance: | Medium → Critical |
importance: | Critical → Medium |
RJ Skerry-Ryan (rryan) wrote : | #36 |
Due to lack of progress, marking Triaged and clearing assignee. Feel free to revert if it is in fact still in progress :).
Changed in mixxx: | |
assignee: | Daniel Schürmann (daschuer) → nobody |
status: | In Progress → Triaged |
Changed in mixxx: | |
milestone: | 2.0.0 → none |
Swiftb0y (swiftb0y) wrote : | #37 |
Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https:/
lock status: | Metadata changes locked and limited to project staff |
Without the --developer flag Mixxx does not crash
Attached the log a non crashing run.