Bug 566773 - Unble to edit file because of constant "Notifying selection listeners" pop-up
Summary: Unble to edit file because of constant "Notifying selection listeners" pop-up
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: Next   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-08 06:59 EDT by Robert Luberda CLA
Modified: 2021-03-15 11:55 EDT (History)
2 users (show)

See Also:


Attachments
log files (57.00 KB, application/x-zip-compressed)
2020-09-08 06:59 EDT, Robert Luberda CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Luberda CLA 2020-09-08 06:59:09 EDT
Created attachment 284078 [details]
log files

It's impossible to edit one, particular .cpp file in Eclipse, because it displays "Notifying selection listeners" pop-up after every single letter entered. 
This happens in eclipse 2020-06, but it used to happen in 2020-03 as well.
I'm attaching full logs.  

Oh, this might be related to the fact the file had some invalid cpp syntax in there, as I was in a middle of ome major refactorings, etc. 
Anyway after I fixed the syntax in some external editor, the issue stopped to re-occurring. But IMHO it is still unacceptable for editor to bail out, only because it cannot properly parse a file. 

If some internal error occurs, then it should stop analyzing the syntax in the file instead of displaying tons of useless pop-ups, especially that a user can do nothing about them.
Comment 1 Jonah Graham CLA 2020-09-08 11:04:17 EDT
Robert, Thank you for your report. I agree that it is not working properly that you are getting constant pop-ups. The root cause is indeed some type of failure to parse, and indeed a failure to parse a single file should not be a catastrophic failure.

We have three bugs this year along the same lines of pop-ups getting in the way. I will use this bug to track the usability, those other bugs can track the specific failures to parse. 

I have put a call out on cdt-dev to see if I can get a better understanding of why this is happening - and to understand if we can actually recover from a stack-overflow error gracefully.
Comment 2 Jonah Graham CLA 2021-03-15 11:55:33 EDT
This bug certainly still exists. But there are no resources forthcoming from the CDT community to fix this particular issue at the moment.