| Summary: | Safari 5.1.1 with Sun JRE crashes Eclipse | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Justin Spadea <jspadea> |
| Component: | EDT | Assignee: | pf yu <pfyu> |
| Status: | REOPENED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chenzhh, huozz, jinfahua, smythew, svihovec |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Justin Spadea
I tried this on Windows XP 32 bit with Sun JRE 1.6 and Safari 5.1.1 and could not reproduce this. Can someone who's hitting this problem provide their detailed machine info? Justin, Today I spent some time on reading the log files, and make sure that the problem only happens with WebKit. In both Xiaobin & my log files, following similar log entries can be found. ---------------------------------------------------- ...... # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0d101e5d, pid=4608, tid=5808 # # JRE version: 6.0_29-b11 # Java VM: Java HotSpot(TM) Client VM (20.4-b02 mixed mode windows-x86 ) # Problematic frame: # C [JavaScriptCore.dll+0x91e5d] ...... ---------------------------------------------------- The JavaScriptCore.dll file is provided by Safari. It looks like sometimes you can reproduce the problem by opening lots of handlers with preview mode, and then keep opening & closing other handlers can duplicate the problem. I talked with Will about this, and he has been using WebKit successfully over the past few days. It could be that the performance fixes we we made in the VE have resolved the WebKit issues. I am closing this defect as resolved indirectly for now. Please re-open if the problem occurs again. Closing. Customer found the similar issue, please refer to the http://www.eclipse.org/forums/index.php/m/771346/#msg_771346 for the detailed information. From user attached log file, it was caused by using the WebKit framework. What is going to be the fix for this problem? Hi, Will It is a eclipse core, or maybe safari defect, Google GWT has the similar problem. I have open a Bug 368648 to eclipse core to get their help. I will check the status of the defect. it is a SWT problem, Bug 368648 has reported to SWT team, it will be fixed after 368648 is solved, so change the target to future. lowering severity to Normal, as this problem only occurs with a limited SW configuration. |