Bug 292306 - [Browser] Eclipse Internal Browser To Be Run as an External Process
Summary: [Browser] Eclipse Internal Browser To Be Run as an External Process
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-14 15:39 EDT by Edwin Chan CLA
Modified: 2019-09-06 16:16 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Chan CLA 2009-10-14 15:39:37 EDT 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: 20080617-2000

Opening this enhancement as requested by SWT.

As seen in bugzilla 290132,  there are customer scenarios where the SWT Browser ran out of memory and caused Eclipse to crash.

The SWT browser is running within a JVM process.  The problem with this current approach is that a process only has so much memory available.  The more you allocate to the heap, the less memory is available for native code to run in the process.

A possible solution for Eclipse is to run the SWT browser in an external server process.



Reproducible: Sometimes
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:16:36 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.