Welcome to the MacNN Forums.

inkhead · Jan 4, 2006, 05:15 AM

Ever since you’ve enable SVG by default all the computer systems I test webkit on, with my normal array of sites, beachball out of control and crash constantly… This morning I took a powerbook and loaded theregister.com and it started beachballing, I decided to let it sit…. 6 hours later i returned to Webkit still beachballing… I think this has something to do with adding SVG into the main webkit body, I would seriously consider removing SVG code until you can fix stability

Anyone else having similar experiences?

Thinine · Jan 4, 2006, 05:49 AM

No. Delete your build product and rebuild from scratch.

inkhead · Jan 4, 2006, 06:43 AM

I download the nightly's directly from webkit, I don't build them myself. I can reproduce the behavior on over a dozen machines.

Prebuild download from apple:
http://nightly.webkit.org/builds/

inkhead · Jan 4, 2006, 06:46 AM

Example Crash:

Date/Time: 2006-01-04 02:44:31.943 -0800
OS Version: 10.4.3 (Build 8F46)
Report Version: 3

Command: Safari
Path: /Applications/Safari.app/Contents/MacOS/Safari
Parent: WindowServer [70]

Version: 2.0.2 (416.13)
Build Version: 1
Project Name: WebBrowser
Source Version: 4161300

PID: 214
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0000000c

Thread 0 Crashed:
0 com.apple.WebCore 0x0114712c DOM::NodeImpl::dispatchEvent(DOM::EventImpl*, int&, bool) + 316
1 com.apple.WebCore 0x01148878 DOM::NodeImpl::dispatchHTMLEvent(DOM::AtomicString const&, bool, bool) + 88
2 com.apple.WebCore 0x010f2ba0 khtml::HTMLTokenizer::notifyFinished(khtml::Cached Object*) + 212
3 com.apple.WebCore 0x010f8b40 khtml::CachedScript::checkNotify() + 84
4 com.apple.WebCore 0x010f9a34 khtml::CachedScript::data(QBuffer&, bool) + 200
5 com.apple.WebCore 0x010fc6dc khtml::Loader::slotFinished(KIO::Job*, NSData*) + 468
6 com.apple.WebCore 0x0115a408 KWQSignal::callWithData(KIO::Job*, NSData*) const + 136
7 com.apple.WebCore 0x0116303c -[KWQResourceLoader finishJobAndHandle:] + 80
8 com.apple.WebKit 0x003241b8 -[WebSubresourceLoader didFinishLoading] + 80
9 com.apple.WebKit 0x0032b7d4 -[WebLoader connectionDidFinishLoading:] + 44
10 com.apple.Foundation 0x92910cdc -[NSURLConnection(NSURLConnectionInternal) _sendDidFinishLoadingCallback] + 188
11 com.apple.Foundation 0x9290ef48 -[NSURLConnection(NSURLConnectionInternal) _sendCallbacks] + 556
12 com.apple.Foundation 0x9290eca0 _sendCallbacks + 156
13 com.apple.CoreFoundation 0x9075db20 __CFRunLoopDoSources0 + 568
14 com.apple.CoreFoundation 0x9075cf98 __CFRunLoopRun + 452
15 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
16 com.apple.HIToolbox 0x931861e0 RunCurrentEventLoopInMode + 264
17 com.apple.HIToolbox 0x931857ec ReceiveNextEventCommon + 244
18 com.apple.HIToolbox 0x931856e0 BlockUntilNextEventMatchingListInMode + 96
19 com.apple.AppKit 0x93663904 _DPSNextEvent + 384
20 com.apple.AppKit 0x936635c8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
21 com.apple.Safari 0x00007910 0x1000 + 26896
22 com.apple.AppKit 0x9365fb0c -[NSApplication run] + 472
23 com.apple.AppKit 0x93750618 NSApplicationMain + 452
24 com.apple.Safari 0x0000307c 0x1000 + 8316
25 com.apple.Safari 0x00057758 0x1000 + 354136

Thread 1:
0 libSystem.B.dylib 0x9000b208 mach_msg_trap + 8
1 libSystem.B.dylib 0x9000b15c mach_msg + 60
2 com.apple.CoreFoundation 0x9075d114 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x928ed664 -[NSRunLoop runMode:beforeDate:] + 172
5 com.apple.Foundation 0x928ed59c -[NSRunLoop run] + 76
6 com.apple.WebKit 0x00365174 +[WebFileDatabase _syncLoop:] + 172
7 com.apple.Foundation 0x928de6d4 forkThreadForFunction + 108
8 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 2:
0 libSystem.B.dylib 0x9000b208 mach_msg_trap + 8
1 libSystem.B.dylib 0x9000b15c mach_msg + 60
2 com.apple.CoreFoundation 0x9075d114 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x92905b9c +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 264
5 com.apple.Foundation 0x928de6d4 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 3:
0 libSystem.B.dylib 0x9000b208 mach_msg_trap + 8
1 libSystem.B.dylib 0x9000b15c mach_msg + 60
2 com.apple.CoreFoundation 0x9075d114 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9075ca18 CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x92906cdc +[NSURLCache _diskCacheSyncLoop:] + 152
5 com.apple.Foundation 0x928de6d4 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 4:
0 libSystem.B.dylib 0x9002b8a8 semaphore_wait_signal_trap + 8
1 libSystem.B.dylib 0x9003001c pthread_cond_wait + 488
2 com.apple.Foundation 0x928e5840 -[NSConditionLock lockWhenCondition:] + 68
3 com.apple.Syndication 0x9a2cf9ec -[AsyncDB _run:] + 192
4 com.apple.Foundation 0x928de6d4 forkThreadForFunction + 108
5 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 5:
0 libSystem.B.dylib 0x9001f20c select + 12
1 com.apple.CoreFoundation 0x9076f9a8 __CFSocketManager + 472
2 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 6:
0 libSystem.B.dylib 0x9002b8a8 semaphore_wait_signal_trap + 8
1 libSystem.B.dylib 0x9003001c pthread_cond_wait + 488
2 com.apple.Foundation 0x928e5840 -[NSConditionLock lockWhenCondition:] + 68
3 com.apple.AppKit 0x937004dc -[NSUIHeartBeat _heartBeatThread:] + 324
4 com.apple.Foundation 0x928de6d4 forkThreadForFunction + 108
5 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 7:
0 libSystem.B.dylib 0x90053f68 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x900702c8 pthread_cond_timedwait_relative_np + 556
2 ...ple.CoreServices.CarbonCore 0x90b745e4 TSWaitOnSemaphoreCommon + 176
3 ...ple.CoreServices.CarbonCore 0x90b74438 AsyncFileThread(void*) + 56
4 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 0 crashed with PPC Thread State 64:
srr0: 0x000000000114712c srr1: 0x000000000200f030 vrsave: 0x00000000fff00000
cr: 0x22022222 xer: 0x0000000020000007 lr: 0x000000000114712c ctr: 0x00000000913ad088
r0: 0x000000000114712c r1: 0x00000000bfffe420 r2: 0x0000000000000001 r3: 0x000000000727b56c
r4: 0x0000000000000000 r5: 0x00000000bfffe4b8 r6: 0x0000000000000001 r7: 0x0000000043bba70f
r8: 0x00000000913ad090 r9: 0x0000000000000000 r10: 0x0000000043300000 r11: 0x0000000000000108
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000001 r15: 0x0000000000000000
r16: 0x0000000000000001 r17: 0x00000000bffff300 r18: 0x0000000000000000 r19: 0x0000000000592520
r20: 0x0000000000000000 r21: 0x0000000000000000 r22: 0x0000000000000001 r23: 0x0000000000669184
r24: 0x0000000000000001 r25: 0x000000000727b544 r26: 0x00000000bfffe4b8 r27: 0x0000000000000000
r28: 0x0000000000000000 r29: 0x000000000727b540 r30: 0x0000000000000000 r31: 0x00000000010f2ad4

Catfish_Man · Jan 4, 2006, 01:55 PM

Originally Posted by inkhead

That crash has nothing to do with SVG. I suggest filing a bug report on the WebKit bugzilla, preferably with instructions for reproducing the crash, or a reduced testcase.

inkhead · Jan 4, 2006, 05:22 PM

I know the crashes have nothing to do with SVG specifically, but the constant crashing has only happened since they hooked SVG into the main body of code. When Webkit+SVG was separate and you downloaded it browsing normal sites, it did the same thing crashing all the time... It was as if something in the SVG codebase was bad.

Now that they are merged together...

proton · Jan 5, 2006, 04:46 AM

Please log a bug report (instructions at http://webkit.opendarwin.org/quality/reporting.html) with information about the bug. Information for what to put in a bug report is here: http://webkit.opendarwin.org/quality/bugwriting.html

Without a bug report in bugzilla it'll be much less likely anyone will look at your problem (read: nobody will look at it until it affects them).

- proton

Angus_D · Jan 5, 2006, 10:22 AM

Remember that the nightlies are unsupported development versions.

inkhead · Jan 6, 2006, 04:38 AM

Angus, how could i forget? Of course I no they are unsupported. They are released specifically to ASSIST apple in ironing out bugs before release, the whole reason i posted was to see if this is an isolated incident or if others are experiencing this.

as far as a bug report i did that first thing, long before i posted to the forums. i did my part i just wanted to discuss it to see if anyone else was experiencing the same things.