Bug 51123 - [Qt][WK2][Symbian] Crash in QLocalSocket/QLocalServer based implementation of IPC
Summary: [Qt][WK2][Symbian] Crash in QLocalSocket/QLocalServer based implementation of...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P2 Blocker
Assignee: Siddharth Mathur
URL:
Keywords: Qt
Depends on:
Blocks: 50251
  Show dependency treegraph
 
Reported: 2010-12-15 11:43 PST by Siddharth Mathur
Modified: 2011-03-03 12:30 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Siddharth Mathur 2010-12-15 11:43:01 PST
Qt MiniBrowser and QtWebProcess fail to communicate due to a null pointer deref (R0 is zero). I will gather the call stack later after returning from my vacation. 
Based purely on trace messages, the cause might be: 
(a) the socket used by the (unix domain) socket server/client was closed by the "hack" code in qeventdispatcher_symbian.cpp (see the debug message "[Qt Message] exception on 8 [will close the socket handle - hack]") 
(b) one of the Platsec messages preventing QtWebProcess working with the File Server had something to do with the issue. Unfortunately traceCore truncated the messages, grr!

00:06:59.627	*PlatSec* ERROR - Capability check failed - A Message (function number=0x00000016) from Thread QtWebProcess[a000e543]0004::QtWebProcess, sent to Server !FileServer, was checked by Thread efile.exe[100039e3]0001::Main and was found to be missing
00:06:59.629	*PlatSec* ERROR - Capability check failed - A Message (function number=0x00000016) from Thread QtWebProcess[a000e543]0004::QtWebProcess, sent to Server !FileServer, was checked by Thread efile.exe[100039e3]0001::Main and was found to be missing
00:07:00.087	Exc 1 Cpsr=60000010 FAR=00000000 FSR=00000805   
00:07:00.087	 R0=00000000  R1=00515944  R2=00000002  R3=00000000
00:07:00.087	 R4=005159a0  R5=00000000  R6=00000000  R7=00632230
00:07:00.087	 R8=7c76ad50  R9=00633474 R10=00515a54 R11=00000000
00:07:00.087	R12=0062ed98 R13=00515938 R14=7d3279d3 R15=7c76ad30
00:07:00.087	R13Svc=92682000 R14Svc=80060ab0 SpsrSvc=60000010    
00:07:00.087	Thread QtWebProcess::QtWebProcess, KernCSLocked=0   
00:07:00.087	Thread full name=QtWebProcess::QtWebProcess
00:07:00.087	Thread ID=706, KernCSLocked=0   
00:07:00.087	Thread QtWebProcess::QtWebProcess Panic KERN-EXEC 3
00:07:00.088	Thread QtWebProcess::Local-c87a1b20 Panic KERN-EXEC 3   
00:07:00.088	Thread QtWebProcess::0c601e0008200e5d Panic KERN-EXEC 3
00:07:00.088	Thread QtWebProcess::0c6028c85569abf9 Panic KERN-EXEC 3
00:07:00.088	Thread QtWebProcess::0c602e18b8170acb Panic KERN-EXEC 3
00:07:00.249	[Qt Message] exception on 8 [will close the socket handle - hack]
Comment 1 Siddharth Mathur 2010-12-15 11:46:51 PST
For Symbian, we may have to do the CoreIPC using native Symbian RSocket API, or move Qt's implementation of QLocalServer and QLocalSocket to use TCP sockets rather than Unix-domain sockets as is currently the case. OpenC != mission critical stuff. 
(It seems we need reliable as well as asynch message passing here, with a variable size payload, so Symbian message queues don't look like an option)
Comment 2 Markus Goetz 2011-01-05 02:35:33 PST
Related to http://bugreports.qt.nokia.com/browse/QTBUG-16441
Comment 3 Siddharth Mathur 2011-03-03 12:30:45 PST
The Symbian port of WebKit2 is being reworked, so this bug report doesn't need to clog the system at this time. I will reopen later if necessary.