| Huge context file after CVS Checkout causes Eclipse to hang [message #34553] |
Wed, 31 October 2007 14:22  |
Eclipse User |
|
|
|
Originally posted by: lucas.farnach.bison-group.com
Hi,
i experience a problem with Mylyn and the Team Project. If a Mylyn task is
(unintentionally) activated while using CVS checkout/update, the task
context will be filled with all the updated files. In my case the context
file under %workspace%/.metadata/.mylyn/contexts grew to 3 GByte, which
causes Eclipse to hang.
In my opinion the updated CVS files are not part of my Mylyn task unless i
want it explicitly. Mylyn should not do that automatically. I always have
to remember to switch off the task, before using the CVS. This is not
really intuitive in my eyes.
Is there a possibility to disable this behavior?
Thanks
Lucas
|
|
|
| Re: Huge context file after CVS Checkout causes Eclipse to hang [message #35231 is a reply to message #34553] |
Sat, 03 November 2007 02:29  |
| Eclipse User |
|
|
|
Originally posted by: beatmik.acm.org
Hi Lucas,
Yes, this is a long standing and annoying but that is scheduled for the
3.0 cycle (harder to fix than it sounds).
120499: [context] make explicitly created resources interesting, and
ignore others, e.g. from CVS checkout
https://bugs.eclipse.org/bugs/show_bug.cgi?id=120499
We list the need to deactivate the task before checkout in the Tips &
Tricks, but that's no excuse ;) That said, I would like to know exactly
how any context could grow that large because my largest context is 321K
zipped, and that's a very large one. Could you please provide details
on that bug whether it was one file that was that large and what it's
size was?
Mik
Lucas Farnach wrote:
> Hi,
>
> i experience a problem with Mylyn and the Team Project. If a Mylyn task
> is (unintentionally) activated while using CVS checkout/update, the task
> context will be filled with all the updated files. In my case the
> context file under %workspace%/.metadata/.mylyn/contexts grew to 3
> GByte, which causes Eclipse to hang.
> In my opinion the updated CVS files are not part of my Mylyn task unless
> i want it explicitly. Mylyn should not do that automatically. I always
> have to remember to switch off the task, before using the CVS. This is
> not really intuitive in my eyes.
> Is there a possibility to disable this behavior?
>
> Thanks
> Lucas
|
|
|
| Re: Huge context file after CVS Checkout causes Eclipse to hang [message #35645 is a reply to message #35231] |
Mon, 05 November 2007 16:30 |
| Eclipse User |
|
|
|
Originally posted by: lucas.farnach.bison-group.com
Hi Mik
thanks for your fast answer.
> Yes, this is a long standing and annoying but that is scheduled for the 3.0
> cycle (harder to fix than it sounds).
I can imagine that its hard to fix ;-) Perhaps Mylyn should work together
with the Eclipse CVS team? There could be an extension point or a listener
provided by the team plugin, that informs you about any cvs actions. So
you know when to ignore the resource changes. But i guess its not that
easy :)
>That said, I would like to know exactly how any context could grow that large
>because my largest context is 321K zipped, and that's a very large one.
Could >you please provide details on that bug whether it was one file that was
that >large and what it's size was?
I experience this problem if i do following (reproducable):
- activate a task
- Checkout a lot of projects from any CVS server
In my case its about 40 projects containing 29.000 resources. After a
while eclipse will whether hang with OutOfMemory, or just getting
extremely slow. In the second case we could extract the contextfile and it
was even too big for IE to read.
It affected only the one file associated with the task (e.g.:
%workspace%/.metadata/.mylyn/contexts/https%3A%2F%2Fbugs.ecl ipse.org%2Fbugs-199246.xml.zip
). I can imagine that you build up a DOM to read the context which is
always a problem with large files.
Anyway the root problem is the CVS thing. Contexts will never be so large
if you use Mylyn normally.
Hope that helps,
Lucas
|
|
|
| Re: Huge context file after CVS Checkout causes Eclipse to hang [message #584294 is a reply to message #34553] |
Sat, 03 November 2007 02:29 |
 Mik Kersten
Messages: 287
Registered: July 2009 |
Senior Member |
|
|
Hi Lucas,
Yes, this is a long standing and annoying but that is scheduled for the
3.0 cycle (harder to fix than it sounds).
120499: [context] make explicitly created resources interesting, and
ignore others, e.g. from CVS checkout
https://bugs.eclipse.org/bugs/show_bug.cgi?id=120499
We list the need to deactivate the task before checkout in the Tips &
Tricks, but that's no excuse ;) That said, I would like to know exactly
how any context could grow that large because my largest context is 321K
zipped, and that's a very large one. Could you please provide details
on that bug whether it was one file that was that large and what it's
size was?
Mik
Lucas Farnach wrote:
> Hi,
>
> i experience a problem with Mylyn and the Team Project. If a Mylyn task
> is (unintentionally) activated while using CVS checkout/update, the task
> context will be filled with all the updated files. In my case the
> context file under %workspace%/.metadata/.mylyn/contexts grew to 3
> GByte, which causes Eclipse to hang.
> In my opinion the updated CVS files are not part of my Mylyn task unless
> i want it explicitly. Mylyn should not do that automatically. I always
> have to remember to switch off the task, before using the CVS. This is
> not really intuitive in my eyes.
> Is there a possibility to disable this behavior?
>
> Thanks
> Lucas
|
|
|
| Re: Huge context file after CVS Checkout causes Eclipse to hang [message #584474 is a reply to message #35231] |
Mon, 05 November 2007 16:30 |
| Eclipse User |
|
|
|
Originally posted by: lucas.farnach.bison-group.com
Hi Mik
thanks for your fast answer.
> Yes, this is a long standing and annoying but that is scheduled for the 3.0
> cycle (harder to fix than it sounds).
I can imagine that its hard to fix ;-) Perhaps Mylyn should work together
with the Eclipse CVS team? There could be an extension point or a listener
provided by the team plugin, that informs you about any cvs actions. So
you know when to ignore the resource changes. But i guess its not that
easy :)
>That said, I would like to know exactly how any context could grow that large
>because my largest context is 321K zipped, and that's a very large one.
Could >you please provide details on that bug whether it was one file that was
that >large and what it's size was?
I experience this problem if i do following (reproducable):
- activate a task
- Checkout a lot of projects from any CVS server
In my case its about 40 projects containing 29.000 resources. After a
while eclipse will whether hang with OutOfMemory, or just getting
extremely slow. In the second case we could extract the contextfile and it
was even too big for IE to read.
It affected only the one file associated with the task (e.g.:
%workspace%/.metadata/.mylyn/contexts/https%3A%2F%2Fbugs.ecl ipse.org%2Fbugs-199246.xml.zip
). I can imagine that you build up a DOM to read the context which is
always a problem with large files.
Anyway the root problem is the CVS thing. Contexts will never be so large
if you use Mylyn normally.
Hope that helps,
Lucas
|
|
|
Powered by
FUDForum. Page generated in 0.03528 seconds
] 
Search
Help
Register
Login
Home
