Bug 105845 - REGRESSION (r133915-r133995): Javascript overlay not drawing correctly
Summary: REGRESSION (r133915-r133995): Javascript overlay not drawing correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.8
: P1 Critical
Assignee: Nobody
URL: http://www.warcaststudios.com/atom-ic...
Keywords: InRadar, Regression
Depends on: 106329
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-28 20:19 PST by Kevin M. Dean
Modified: 2013-01-08 20:25 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin M. Dean 2012-12-28 20:19:15 PST
Go to the gallery and click on a picture. Overlay window doesn't appear correctly.

May be a similar issue to a previous bug I reported for the same range, but that bug hasn't seen any attention - Bug 103279
Comment 1 Alexey Proskuryakov 2013-01-02 10:10:02 PST
For me, the overlay appears correctly once, but not on subsequent clicks.
Comment 2 Alexey Proskuryakov 2013-01-02 10:10:16 PST
<rdar://problem/12944612>
Comment 3 Kevin M. Dean 2013-01-02 10:41:08 PST
Yeah, sometimes it appears when I come back later or wait a while. If it similar to my other match.com bug, then sometimes just sitting and waiting on the page can cause a different result.

Usually when I start from an empty cache. The white picture window will appear, scale to the left, disappear and just leave a couple of arrow buttons behind. Subsequent clicks cause a window to appear and disappear immediately.
Comment 4 Kevin M. Dean 2013-01-07 20:42:08 PST
r139024 now crashes when trying to view a gallery picture.


Process:         WebProcess [8205]
Path:            /Applications/WebKit.app/Contents/Frameworks/10.8/WebKit2.framework/WebProcess.app/Contents/MacOS/WebProcess
Identifier:      com.apple.WebProcess
Version:         537+ (537.25+)
Code Type:       X86-64 (Native)
Parent Process:  SafariForWebKitDevelopment [8202]
User ID:         501

Date/Time:       2013-01-07 23:38:08.342 -0500
OS Version:      Mac OS X 10.8.2 (12C60)
Report Version:  10

Interval Since Last Report:          1161632 sec
Crashes Since Last Report:           -7
Per-App Interval Since Last Report:  84921 sec
Per-App Crashes Since Last Report:   2
Anonymous UUID:                      3FB4F99D-AA2A-BF09-84EE-B9783AA375CE

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

VM Regions Near 0x18:
--> 
    __TEXT                 000000010845b000-000000010845c000 [    4K] r-x/rwx SM=COW  /Applications/WebKit.app/Contents/Frameworks/10.8/WebKit2.framework/WebProcess.app/Contents/MacOS/WebProcess

Application Specific Information:
Bundle controller class:
BrowserBundleController
 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.JavaScriptCore      	0x000000010890b207 JSC::Arguments::create(JSC::JSGlobalData&, JSC::ExecState*, JSC::InlineCallFrame*) + 199
1   ???                           	0x000000010aa33df6 0 + 4473437686
2   com.apple.JavaScriptCore      	0x00000001089952f4 JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 548
3   com.apple.JavaScriptCore      	0x00000001088a34a5 JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 69
4   com.apple.WebCore             	0x000000010926bf1f WebCore::JSMainThreadExecState::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 143
5   com.apple.WebCore             	0x00000001097d7f7f WebCore::ScheduledAction::executeFunctionInContext(JSC::JSGlobalObject*, JSC::JSValue, WebCore::ScriptExecutionContext*) + 479
6   com.apple.WebCore             	0x00000001097d7c1c WebCore::ScheduledAction::execute(WebCore::Document*) + 156
7   com.apple.WebCore             	0x0000000108f88573 WebCore::DOMTimer::fired() + 323
8   com.apple.WebCore             	0x000000010999e83f WebCore::ThreadTimers::sharedTimerFiredInternal() + 159
9   com.apple.WebCore             	0x0000000109827cb3 WebCore::timerFired(__CFRunLoopTimer*, void*) + 51
10  com.apple.CoreFoundation      	0x00007fff8ef4cda4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
11  com.apple.CoreFoundation      	0x00007fff8ef4c8bd __CFRunLoopDoTimer + 557
12  com.apple.CoreFoundation      	0x00007fff8ef32099 __CFRunLoopRun + 1513
13  com.apple.CoreFoundation      	0x00007fff8ef316b2 CFRunLoopRunSpecific + 290
14  com.apple.HIToolbox           	0x00007fff94dad0a4 RunCurrentEventLoopInMode + 209
15  com.apple.HIToolbox           	0x00007fff94dace42 ReceiveNextEventCommon + 356
16  com.apple.HIToolbox           	0x00007fff94daccd3 BlockUntilNextEventMatchingListInMode + 62
17  com.apple.AppKit              	0x00007fff929ec613 _DPSNextEvent + 685
18  com.apple.AppKit              	0x00007fff929ebed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
19  com.apple.AppKit              	0x00007fff929e3283 -[NSApplication run] + 517
20  com.apple.WebCore             	0x00000001097d39d3 WebCore::RunLoop::run() + 67
21  com.apple.WebKit2             	0x00000001085b443f int WebKit::ChildProcessMain<WebKit::WebProcess, WebKit::WebProcessMainDelegate>(WebKit::CommandLine const&) + 575
22  com.apple.WebKit2             	0x0000000108557557 WebKitMain + 299
23  com.apple.WebProcess          	0x000000010845be7b main + 214
24  libdyld.dylib                 	0x00007fff904cc7e1 start + 1
Comment 5 Alexey Proskuryakov 2013-01-07 22:05:48 PST
> r139024 now crashes when trying to view a gallery picture.

Can you please file a new bug about this issue? It is OK that this one will be impossible to reproduce for the time being - but tracking both issues in one bug would be very confusing.
Comment 6 Kevin M. Dean 2013-01-08 08:48:16 PST
(In reply to comment #5)
> > r139024 now crashes when trying to view a gallery picture.
> 
> Can you please file a new bug about this issue? It is OK that this one will be impossible to reproduce for the time being - but tracking both issues in one bug would be very confusing.

See Bug Bug 106329
Comment 7 Kevin M. Dean 2013-01-08 19:52:22 PST
r139137 now works fine. Maybe that other bug fix also benefitted the ultimate issue that was causing this bug as well.
Comment 8 Alexey Proskuryakov 2013-01-08 20:25:27 PST
Curious. I also cannot reproduce with r139111.