Bug 115100

Summary: [Qt][Win] QtTestBrowser crashing
Product: WebKit Reporter: Zoltan Arvai <zarvai>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: allan.jensen, hausmann, jturcotte, kadam, ossy
Priority: P2 Keywords: Qt
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Description Zoltan Arvai 2013-04-24 05:12:21 PDT
QtTestBrowser crashing on startup with win build (r148954) / Qt5.0.1. It is the same on 32 and 64 bit, too. MiniBrowser seems fine.

64bit:

Problem signature:
Problem Event Name: APPCRASH
Application Name: QtTestBrowser.exe
Application Version: 0.0.0.0
Application Timestamp: 517668a6
Fault Module Name: Qt5WebKit.dll
Fault Module Version: 5.0.1.0
Fault Module Timestamp: 5176682e
Exception Code: c0000005
Exception Offset: 000000000002ea43
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional Information 1: 186e
Additional Information 2: 186ebcdcf25a9ba59a26bb1baa9e0845
Additional Information 3: 918e
Additional Information 4: 918e061f4afe3fe36bdce78807d4af36

I'll try to find the revision that made it crashing.
Comment 1 Zoltan Arvai 2013-05-10 09:13:56 PDT
Interesting. The same revision at one time runs fine, but other time crashes on start. Both case I did clean build. I'll compare binaries to see if there is a difference between the resulted files.
Comment 2 Csaba Osztrogonác 2013-05-13 09:57:35 PDT
Doesn't http://trac.webkit.org/changeset/150021 fix this bug?
Comment 3 Jocelyn Turcotte 2013-05-14 02:18:04 PDT
(In reply to comment #2)
> Doesn't http://trac.webkit.org/changeset/150021 fix this bug?

Since there is no stack trace it's difficult to tell, but the symtoms fit quite well and I'll assume so.
Please reopen if the crash wasn't involving FrameLoaderClientQt.
Comment 4 Zoltan Arvai 2013-05-16 06:40:20 PDT
(In reply to comment #3)
> (In reply to comment #2)
> > Doesn't http://trac.webkit.org/changeset/150021 fix this bug?
> 
> Since there is no stack trace it's difficult to tell, but the symtoms fit quite well and I'll assume so.
> Please reopen if the crash wasn't involving FrameLoaderClientQt.

Probably it's fine now. I had no crash after that fix.