Community
Participate
Working Groups
Build Identifier: 3.8M2 That's all; I got a Norton dialog telling me that eclipse was removed because of "suspect behaviour". Reproducible: Always Steps to Reproduce: 1.just start the eclipse.exe 2. 3.
This doesn't look like an Eclipse bug. You should try adding javaw.exe or eclipse.exe as exceptions in Norton Antivirus. I intend to close as INVALID Just curious btw, did you start noticing this only from 3.8M2?
All other (own) JAVA applications run OK; on Windows 7 Norton acts exactly the same. On another system AVG (free edition) which is known to be over-vigilant, does not interfere and eclipse runs OK. May be another reason to turn from Norton to AVG again. ;JFL.
P.S.: the test on Windows 7 was done with 64-bits JAVA and 64-bits eclipse 3.8M2 All tests were done with JAVA 1.6.0_27 ;JFL.
P.S.: forgot to answer your question: All versions of eclipse till now run OK (tried all stable builds over the years). ;JFL.
I do have Norton Antivirus but don't see this behavior. What is there in the logs? It may be worth checking with Norton. Moving to Platform to see if they have any comments?
Did you run a checksum verification on your download?
1) Log is terse: (translated) "Suspect behaviour of eclipse.exe by module SONAR" SONAR seems to be a part of NORTON Internet Security 2011. Remarks: "Very few users, risk is high, source unknown". 2) the download was checked and repeated to be sure. ;JOOP!
(In reply to comment #7) Thanks for more information. I have submitted this problem to https://submit.symantec.com/false_positive. At the same time, I think eclipse.exe doesn't have a company name on windows. I think this should be mentioned to avert some checks. This is in Equinox/Launcher and hence moving there now :).
Update: I got loads of anti-virus updates on my Windows 7 laptop. Now it looks like 3.8M2 runs OK on it (all 64-bits). I was able to 'clean' all my projects with the correct error/warning counts afterwards. XP still fails to run 3.8M2 Question: should I upgrade to 4.2M2? ;JOOP!
(In reply to comment #9) > Update: I got loads of anti-virus updates on my Windows 7 laptop. > Now it looks like 3.8M2 runs OK on it (all 64-bits). > I was able to 'clean' all my projects with the correct error/warning counts > afterwards. > > XP still fails to run 3.8M2 Just to make sure I understand. 3.8 M1 works just fine for you on XP? > > Question: should I upgrade to 4.2M2? We encourage all the community to use 4.2 for the Juno release. But I suspect the issue would be identical for the 4.2 builds since the launcher is identical between the 3.8 and 4.2 builds in Juno. > > ;JOOP!
Confirmed: 3.8M1 works fine. I must confess that once a month I have to stop and start again (on all OS's) because it intermittently may come up with >1000 errors, but that's a different story. I will give 4.x a try this week. ;JOOP!
Well ....... I concentrate on XP now, because the problem restricts itself to the 32-bit version of ECLIPSE: 3.8M1 : OK 3.8M2 : removed by NORTON.SONAR 4.1 : OK! 4.2M1 : OK! 4.2M2 : removed by NORTON.SONAR Weird. So, I'll stick to 4.2M1 and await 4.2M3 or such. Remark: why do 4.2M1 and (for some seconds) 4.2M2 show a 4.1-splash???? ;JOOP!
Sorry that I have to say it, but 4.2M1 is sick of bugs: wrong colors, wrong views ... I'm going back to 3.8M1 and will forget about the whole case. Until now I always instantly upgraded to the newest stable build but this has cost me and you useless time. You may close the bug. ;JOOP!
(In reply to comment #12 > Remark: why do 4.2M1 and (for some seconds) 4.2M2 show a 4.1-splash???? 4.2 has not gone GA yet and we have not had the time to update the splash screen yet. See bug 354997. (In reply to comment #13) > Sorry that I have to say it, but 4.2M1 is sick of bugs: wrong colors By default we use a different theme for 4.x. If you would prefer the classic theme, you can change it back. 1. Window > Preferences > General > Appearance 2. From the combo box, select 'Classic'. > , wrong views ... Please do not hesitate to open bugs you encounter with 4.2's milestone releases.
Sorry, I was not clear enough. Of course I chose 'Classic' from the beginning, because I like edges between the views. I encountered 2 major problems (please advise me if I should submit a bug or rather correct myself): 1) arranging views in JAVA perspective appeared to spoil views in Debug perspective and reverse. 2) I like the active tab black on yellow but whatever color I chose it remains kind of purple blue. May be this is related to the fact that I 'ran with' my 3.8 .metadata directory. Concluding: eclipse has been and still is the best software product I have ever used in my 35-year career and now that I'm retired, being able to use it for the rest of my life, means a great deal to me. I do hope it will never end. ;JOOP!
(In reply to comment #15) > 1) arranging views in JAVA perspective appeared to spoil views in Debug > perspective and reverse. This definitely sounds like a bug as changing the layout of one perspective should not affect the other. That is, of course, unless you are moving items within the shared area itself. Please open a bug against Platform UI describing what you did. Screenshots would also be very helpful, thank you. > 2) I like the active tab black on yellow but whatever color I chose it remains > kind of purple blue. The colours are defined by CSS. Bug 344234 has some information on that topic in general.
Going back to the topic of this bug. I don't think we should close it since something in the launcher has changed from Juno M1 to M2 that is causing this issue to arise. We need to understand what that is.
(In reply to comment #8) > (In reply to comment #7) > Thanks for more information. I have submitted this problem to > https://submit.symantec.com/false_positive. Symantec has come back and told that they have removed this detection and the latest update should work fine. Can you please check after updating your antivirus?
Verified: 3.8M2 now runs OK on XP. B.t.w.: Norton Internet Security 2011 updates every 5 minutes (!?!). Thanks to all of you who spent time on this topic. ;JOOP!
Breaking news (a problem shared is a problem halved): the latest update of Microsoft anti-virus removes Chrome! ;JOOP!
Given this bug's age, and comment 18 and 19, I think we should close as "not eclipse". (It'd be nice to know the pattern or change that caused it ... but, doubt a security company would want to say exactly what they are checking). But feel free to re-open, Tom, if you still feel as you did in comment 17. To cross reference, see also bug 428639 and bug 429175.
