recent build - osx crashes 10.7 #1226
Comments
miguel-negrao
added
bug
|
Miguel - If you want to test on the latest qt5, I just switched it to use a 10.7 http://supercollider.s3.amazonaws.com/builds/supercollider/supercollider/osx/qt52-latest.html A little searching shows that a common chokepoint for Qt crashes, I'm close (this afternoon?) to committing a change to add basic sclang unit
On Sun, Nov 2, 2014 at 12:46 PM, Miguel Negrão notifications@github.com
|
|
Hi Scott, Thanks for updating the qt branch. I tried the qt sc binary, but unfortunately it was not possible to use it due a lot of problems:
I had a crash together with strange behaviour where some 8 icons for sc appeared in the doc all trying to start at the same time. crash report attached.
|
|
(1) Can you check which font is being used, in the Editor preferences? I believe by default it's just looking for the default mono font, which may differ in 10.7? I was about to propose a change that bundled a decent code font in SC, to keep a consistent (and consistently non-ugly) look across platforms, maybe that would solve.... (2) multiple icons - were you doing something that would have caused sclang or scserver to repeatedly (re)launch, spawn multiple servers, or something else similar? (3) I recently pulled a change from Tim that fixed the Cmd+Period problem you're describing - I haven't tested it yet, though, it might not be working properly. If you need a workaround for now, changing it to Cmd+Shift+period in the keyboard shortcuts works. |
|
|
Btw, the crash is reproducible, it happens every time I open a score in Unit Lib, but I don't have a simple reproducer. Unit Lib involves a lot of code, not sure what exactly triggers the crash. Right now the cras makes sc with qt5 on osx 10.7 unusable for unit lib users. I can look later if the same crash happens in linux too with qt5. |
Of course, this function is used precisely for signalling between threads, so this is not informative. I doubt that this is a bug in the Qt framework as this is one of the very core functionalities of the framework that has been around since its version 1. Someone should debug this with a proper debug build and see if there are any funny pointers in the function QtCollider::QObject_Finalize which in turn calls QCoreApplication::postEvent. |
|
Most likely, the QObject that is being finalized was not used correctly in some C++ code and was perhaps already deleted at the point when the finalizer runs and tries to post en event on the already-deleted object. |
|
@miguel-negrao - see if this addresses the crash: |
|
Yes, indeed the crash was after using a dialog. That build didn't crash anymore during a roughly one hour session, thanks. I got the impression that pen drawing was a bit slower, but don't have any numbers to back that up. There's still the weird issue of scscynth and sclang appearing as "SuperCollider" in the dock and Activity Monitor. |
|
can this be closed? |
The original crash is still happening (in qt4). |
|
And in Qt5? |
|
Didn't we drop 10.7 support?
|
I don't have access to osx at the moment, but I think what I said above is that the patched version by scztt wasn't crashing anymore on qt5. Since we are moving to qt5, I suppose we can close this. |
|
Okay! |
Hi
I've been using a recent build from travis (29 october) on osx 10.7 and I get crashes like the one below like once per hour. Seem related to Qt. Couldn't test if they also occur with qt5 since the qt5 branch doesn't build for 10.7. Perhaps that could be fixed, so I could test the qt5 branch in this system to see if the issue disappears ?
The crash seems to always be like this:
The text was updated successfully, but these errors were encountered: