Custom Query (301 matches)

Hi/2.

When using an embedded window on DIVE mode, the following crash occurs on exit.

Killed by SIGSEGV
pid=0x0569 ppid=0x002b tid=0x0001 slot=0x00b9 pri=0x0200 mc=0x0001
G:\APPS\QT4\SMPLAYER\SMPLAYER.EXE
QTCORE4 0:00174652
cs:eip=005b:12ae4652      ss:esp=0053:00a6fba0      ebp=00a6fbd8
 ds=0053      es=0053      fs=150b      gs=0000     efl=00012206
eax=20067d80 ebx=2034cc40 ecx=ffffffff edx=20259f4c edi=00000000 esi=2034cc40
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

Setting QT_PM_NO_DIVE=1 prevents this crash.

Used revision is r801.

Reported by Alex Tailor in gmane.org.netlabs.qt.devel:

Attempting to mark text in any QT text control using Shift + the keypad navigation keys results in numbers being printed instead. (In other words, Shift has the effect of simulating NumLock? instead of marking.)

This rather unfortunately makes it difficult to effectively use QT text controls...

Using 4.6.2.

I can confirm that.

With I compare my current 4.6.3 build with an older 4.6.2 I notice a performance degration in Arora. Basically, when the page load progress reaches about 60%, the CPU load maxes out and stays there for a while. After that, the page is shown correctly. With 4.6.2 this CPU load peak is there as well, but smaller and shorter.

It seems to be especially visible when a page is loaded for the first time after Arora has been started. Also it might depend on the page. I saw it with ​http://www.commtalk.org/ and ​http://www.s-t.de/ .

Could someone of you try to compare Arora's loading performance running on top of 4.6.3 and 4.6.2 ? Especially the sequence: start the program - goto one of the mentioned URLs.