Bug 273692

Summary: Application with SWT, xulrunner and javaxpcom hangs / crashes
Product: [Eclipse Project] Platform Reporter: Sunitha <sunitha.kurapati>
Component: SWTAssignee: Grant Gayed <grant_gayed>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: P3 Keywords: needinfo
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
error file with xulrunner 1.9.2a1pre and swt 3.5M6 on windows
none
error file with xulrunner 1.8.1.3 on windows
none
error file with swt 3.2.1 and xulrunner 1.8.1.3 on linux none

Description Sunitha CLA 2009-04-25 16:05:22 EDT 
Our web crawler application is built using SWT, javaxpcom and xulrunner. On both windows and linux it hangs with xulrunner 1.8.1.3 and SWT 3.2.1, 3.3, 3.4 and 3.5 milestone versions. It crashes when we try with xulrunner 1.9.x and above SWT versions. On both platforms it does not happen right away. It crawls through around couple of thousand web pages (Say for running about 1 and half hours) it hangs or crashes. Please find the attached hs_err_pid files for both xulrunner 1.8.1.3 and xulrunner 1.9.2a1 nightly build. We use jdk1.5.0_15 on windows and jre 1.5.0_18 on linux. It's really urgent and appreciate any kind of help on this.
Comment 1 Sunitha CLA 2009-04-25 16:07:45 EDT 
Created attachment 133228 [details]
error file with xulrunner 1.9.2a1pre and swt 3.5M6 on windows
Comment 2 Sunitha CLA 2009-04-25 16:08:42 EDT 
Created attachment 133229 [details]
error file with xulrunner 1.8.1.3 on windows
Comment 3 Sunitha CLA 2009-04-25 16:09:38 EDT 
Created attachment 133230 [details]
error file with swt 3.2.1 and xulrunner 1.8.1.3 on linux
Comment 4 Grant Gayed CLA 2009-04-27 10:20:25 EDT 
The traces are not very helpful because they all crash in the event loop.  A reproducable case is needed that can be run here that makes the crash happen.  Can you provide this?
Comment 5 Grant Gayed CLA 2010-05-27 12:33:23 EDT 
Timed out, closing report.  If there is more feedback available such as a reproducable case of this problem then please reopen this report, thanks.