Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 508916

Summary:

content-assist window causes freeze

Product:

[Eclipse Project] Platform

Reporter:

Martin Lippert <mlippert>

Component:

SWT

Assignee:

Platform-SWT-Inbox <platform-swt-inbox>

Status:

CLOSED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

david_syer, ericwill, kdevolder

Version:

4.6

Keywords:

triaged

Target Milestone:

---

Hardware:

Macintosh

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
thread dump while freeze	none

Description Martin Lippert

2016-12-08 10:15:26 EST

Dave (Syer) reports about a repeating freeze of his Eclipse/STS installation and it seems to be caused by some native SWT code (maybe). The thread dump (is attached to this bug) doesn't reveal much information, but it seems to be a very annoying problem for him. Would be great if we could find out what is going wrong here. It is not fully reproducable with exact steps, but seems to happen quite often for him.

Comment 1 Martin Lippert

2016-12-08 10:16:17 EST

Created attachment 265771 [details]
thread dump while freeze

Comment 2 Leo Ufimtsev

2016-12-08 11:15:40 EST

I can't see anything particularly interesting.

In the interest of investigation:
- Is this on Gtk3? 
- Does it occur on gtk2?

What OS, version of gtk does he use?

Comment 3 Kris De Volder

2016-12-08 18:28:24 EST

Similar to this old bug: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=354842

Many folks have experienced it. I experience it almost on a daily basis. In my case happens always when I am dragging mouse around and happen to accidentally 'touch' CTRL key. I beleave it specifically happens when a popup for hyperlink navigation was about to show. I'm on Ubuntu 14.04. Dave's on Ubuntu 16.04. The fact that Dave is getting this on, seems like, *normal* content-assists is very worrysome (completions popups don't trigger this for me). If completions can now trigger this, I expect the frequency with which people will hit this problem to increase tenfold.

Don't know about Dave, but I'm using GTK 3 nowadays. GTK 2 is pretty much unusable as its even more glitchy than GTK 2 nowadays (used to be the reverse some months ago)

Comment 4 Eric Williams

2019-01-08 17:13:51 EST

Is this still reproducible? Sounds like an old WebKit 1 crash (we use WebKit 2 now).

Comment 5 Kris De Volder

2019-01-08 18:09:48 EST

Anecdotally, I haven't experienced this particular bug in a long time.

Nowadays I am using GTK3, Eclipse 4.10 on Ubuntu 18.04.1

Comment 6 Eric Williams

2019-01-09 10:27:06 EST

(In reply to Kris De Volder from comment #5)
> Anecdotally, I haven't experienced this particular bug in a long time.
> 
> Nowadays I am using GTK3, Eclipse 4.10 on Ubuntu 18.04.1

Okay. I am going to close this bug as it sounds like WebKit1 crash. If the issue happens again with WebKit2, please re-open this ticket.