I'm still working with the public preview, and we're seeing sporadic crashes with stack traces that end similarly to:
#0 0x00007fff84669aef in objc_msgSend () #1 0x00007fff83886cd0 in -[NSArray containsObject:] () #2 0x00007fff80fb7749 in -[NSTSMInputContext initWithClient:] () #3 0x00007fff80fb7556 in +[NSInputContext inputContextWithClient:] () #4 0x00007fff80f021c6 in -[NSView inputContext] () #5 0x00007fff80e75c2f in +[NSInputContext currentInputContext] () Most often, this is happening directly below QMacInputContext::reset(), but we have seen it being triggered just in normal event processing under [NSApplication updateWindows] after drag & drop operations. Failures under QMacInputContext::reset() are similar to: #0 0x00007fff84669ad9 in objc_msgSend () #1 0x00007fff83886c52 in -[NSArray containsObject:] () #2 0x00007fff80fb7749 in -[NSTSMInputContext initWithClient:] () #3 0x00007fff80fb7556 in +[NSInputContext inputContextWithClient:] () #4 0x00007fff80f021c6 in -[NSView inputContext] () #5 0x00007fff80e75c2f in +[NSInputContext currentInputContext] () #6 0x0000000147664574 in QMacInputContext::reset () The Objective C selector is frequently, but not always, "countByEnumeratingWithState:objects:count", and often a QWidget is being destroyed further up the stack. Smells like memory corruption, possibly caused by an under-retained object. Is this a known issue (and if so, is it already addressed in the beta?) If not, is there any other info I can provide to help chase it down? I don't have clear reproduction steps as of today, unfortunately. -- Dennis Dennis J. Wilkinson, II Graphical Languages UI Engineer The MathWorks, Inc. [email protected] _______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
