Closed (duplicate)
Project:
Drupal core
Version:
6.x-dev
Component:
javascript
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2008 at 09:40 UTC
Updated:
12 Jan 2008 at 08:14 UTC
Jump to comment: Most recent file
Comments
Comment #1
dsp1 commentedi checked my log and it showed javascript. so I disabled javascript in safari and no crash.
i also tested other areas. with javascript turned on , it crashes on many admin pages including blocks, user>access rules, etc.
Comment #2
stborchertCould you please post the messages written to your log file. Otherwise it could be very difficult to reproduce.
thanks,
Stefan
Comment #3
dsp1 commentedhere is the log. i will spare you the repeated threads, but threads 2 and 3 repeat 250 times each with the final number 508. unfortunately it does not show which script is the last to run. only six js files were changed from rc1 to rc2 in misc folder. i would venture to guess it is one of the six.
Version: 2.0.4 (419.3)
Build Version: 31
Project Name: WebBrowser
Source Version: 4190300
PID: 711
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xbf7ffe0c
Thread 0 Crashed:
0 com.apple.JavaScriptCore 0x952f64fb match + 12
1 com.apple.JavaScriptCore 0x952f73d5 match + 3814
2 com.apple.JavaScriptCore 0x952f667d match + 398
3 com.apple.JavaScriptCore 0x952f73d5 match + 3814
Comment #4
scor commentednot able to reproduce this on safari 3.0.4 (523.12). is there any way to downgrade to safari 2 on mac OS X 10.4.11 to try to reproduce this?
Comment #5
stborchertI couldn't check it here but you should be able to uninstall safari 3 (uninstaller is shipped within dmg).
btw:
http://lists.apple.com/archives/client-management/2008/Jan/msg00023.html
Comment #6
catchdps1, do you have any browser plugins installed?
Comment #7
dvessel commentedHaven't tried yet.. http://michelf.com/projects/multi-safari/
There are some issues with Leopard so I'm waiting until they iron that out even though there's a workaround.
Comment #8
scor commentedthanks dvessel for the link. I can definitely reproduce this on safari 2.0.4 (419.3), and the previous versions of safari 2 are also unstable, especially when tableheader and tabledrag are used together (blocks).
It seems that the jquery clone() of tableheader.js is the problem: no crash when
clone(true)is removed. No crash either when using the previous version of tableheader.js (1.9).Comment #9
chx commentedDo we need to support Safari 2?
Comment #10
scor commentedI was actually wondering is safari 2 was still used by many people, given that safari 3 is now shipped with mac os since Mac OS X Update 10.4.11
We still need to disable the tableheaders for safari 2 though.
Comment #11
mfer commentedI think we still need to support safari 2. There are a lot of people who still use it. Not as many as IE 6. But, we don't want to be a platform that isn't supporting it.
Comment #12
dvessel commentedWe shouldn't bend over backwards to support it. It was always a buggy browser and as scor mentions, Safari 3 is an automatic download with 10.4. Since I caused the problem, I'll try to find a fix. If a workaround is not easy, I think we should treat it like IE6.. Just disable it.
Comment #13
mfer commentedThat's support enough for me :-)
Comment #14
scoutbaker commented+1 for treating Safari 2 like IE6 if there isn't an easy workaround. Graceful degradation is good.
Comment #15
dvessel commentedThis does it for me. Very simple fix. It wasn't just the clone. It was the long chain of commands it didn't like.
Comment #16
m3avrck commentedSince headerClone is already a jQuery object, calling $(headerClone) is unecessary (and a tad slower).
Should work better.
Comment #17
dvessel commentedGreat, thanks for the advise.
Comment #18
dvessel commentedChanging status due to this issue. That'll be fixed first since it's the same area of code that needs to be changed.
Comment #19
dvessel commentedThe fix for the default radio select patch seems to fix the crashes also. Please test it out.
http://drupal.org/node/208179
Comment #20
dsp1 commentedapplied the patch from the other node and no crashes. thanks dvessel for the fast fix.