Nokia considers this bug not being their problem, but a webkit issue. Therefore I filed a new bug report for webkit.
https://bugs.webkit.org/show_bug.cgi?id=57729 Let's see what happens now On 03/28/2011 03:11 AM, Gelonida Gmail wrote: > On 03/27/2011 10:52 PM, Hans-Peter Jansen wrote: >> On Saturday 26 March 2011, 23:45:04 Gelonida Gmail wrote: >>> I wrote also an equivalent C++ version, and managed to crash it >>> (though I had to try over 10 times before I got a segfault) >> >> Well, I can always reproduce a crash be simply logging in, and when the >> request for permission of Heroic! is requested, just click on start >> page at the top. During display of the homepage, it crashes reliable >> here for both the PyQt and the Qt version: >> >> #0 0xb702ac80 in >> JSC::Interpreter::prepareForRepeatCall(JSC::FunctionExecutable*, >> JSC::ExecState*, JSC::JSFunction*, int, >> JSC::ScopeChainNode*, JSC::JSValue*) () from /usr/lib/libQtWebKit.so.4 >> #1 0xb70964a7 in JSC::JSArray::sort(JSC::ExecState*, JSC::JSValue, >> JSC::CallType, JSC::CallData const&) () >> from /usr/lib/libQtWebKit.so.4 >>> >>> Will now look, where I can post the Qt bug >> >> I've added my observations there, too. >> > > Thanks, It's always better if at least two independent persons can > confirm a problem. > > >>> I filed a bug report: >>> >>> http://bugreports.qt.nokia.com/browse/QTBUG-18390 > > > Let's see when we get first feedback of the Qt team . > As this is the first issue I reported I have now experience about the > responsiveness concerning this kind of bugs. > > > > > > _______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt