My schedule is for the next 2 wks will be focused on some contract work I have to deliver So I'm not sure how much time I will have to tackle pgRouting issues.
I think I can work in looking at the new TSP issues for that starts. My next major pgrouting task is to look at them memory issues that are causing crashes and std::bad_alloc issues. I'm not looking forward to this task because the problems seems to be intermitent and the fact that is works in one setup does not mean that you have solved the problem. I also think this is related to postgresql palloc usage and subtle issues related to that.
My schedule is for the next 2 wks will be focused on some contract work I have to deliver So I’m not sure how much time I will have to tackle pgRouting issues.
I think I can work in looking at the new TSP issues for that starts. My next major pgrouting task is to look at them memory issues that are causing crashes and std::bad_alloc issues. I’m not looking forward to this task because the problems seems to be intermitent and the fact that is works in one setup does not mean that you have solved the problem. I also think this is related to postgresql palloc usage and subtle issues related to that.
I will try to fix Windows/Mac related critical issues at next week.
Regards,
2013/6/27 Stephen Woodbridge <woodbri@swoodbridge.com <mailto:woodbri@swoodbridge.com>>
Hi All,
Dave P. - thanks for the TSP problem reports.
Nagase-san - thank you for the crash reports.
My schedule is for the next 2 wks will be focused on some contract
work I have to deliver So I'm not sure how much time I will have
to tackle pgRouting issues.
I think I can work in looking at the new TSP issues for that
starts. My next major pgrouting task is to look at them memory
issues that are causing crashes and std::bad_alloc issues. I'm not
looking forward to this task because the problems seems to be
intermitent and the fact that is works in one setup does not mean
that you have solved the problem. I also think this is related to
postgresql palloc usage and subtle issues related to that.
Thanks,
-Steve
_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org <mailto:pgrouting-dev@lists.osgeo.org> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
--
Ko Nagase (sanak)
Georepublic Japan
mail: geosanak@gmail.com <mailto:geosanak@gmail.com>
nagase@georepublic.co.jp <mailto:nagase@georepublic.co.jp>
Sorry, I just started to check new pgRouting 2.0 and its issues,
but, if you use Linux(Ubuntu .etc), it seems that there is no reported issue about ksp memory problems.
My schedule is for the next 2 wks will be focused on some contract work I have to deliver So I’m not sure how much time I will have to tackle pgRouting issues.
I think I can work in looking at the new TSP issues for that starts. My next major pgrouting task is to look at them memory issues that are causing crashes and std::bad_alloc issues. I’m not looking forward to this task because the problems seems to be intermitent and the fact that is works in one setup does not mean that you have solved the problem. I also think this is related to postgresql palloc usage and subtle issues related to that.
All I was trying to say was that during my development of the KSP wrapper I had some memory problems, I resolved them. Before submitting the code. As far as I am aware there are no memory issues with the ksp code.
I was wondering what the memory problems were with the tsp code.
regards
Dave.
Hi Dave,
Sorry, I just started to check new pgRouting 2.0 and its issues,
but, if you use Linux(Ubuntu .etc), it seems that there is no reported issue about ksp memory problems.
So, in that case, could you create a new issue?
Regards,
2013/6/27 Dave Potts <dave.potts@pinan.co.uk <mailto:dave.potts@pinan.co.uk>>
On 27/06/13 07:07, sanak wrote:
hi
Is there a bug tag with the memory problems ?
I had some rather strange experiences with memory issues when I
was writing the ksp wrapper.
Another gotcha on the web site for getting the source version
refer to 1.0 release and not the development one.
Dave.
Hi Stephen,
Thanks for comment.
I will try to fix Windows/Mac related critical issues at next week.
Regards,
2013/6/27 Stephen Woodbridge <woodbri@swoodbridge.com
<mailto:woodbri@swoodbridge.com>>
Hi All,
Dave P. - thanks for the TSP problem reports.
Nagase-san - thank you for the crash reports.
My schedule is for the next 2 wks will be focused on some
contract work I have to deliver So I'm not sure how much time
I will have to tackle pgRouting issues.
I think I can work in looking at the new TSP issues for that
starts. My next major pgrouting task is to look at them
memory issues that are causing crashes and std::bad_alloc
issues. I'm not looking forward to this task because the
problems seems to be intermitent and the fact that is works
in one setup does not mean that you have solved the problem.
I also think this is related to postgresql palloc usage and
subtle issues related to that.
Thanks,
-Steve
_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
<mailto:pgrouting-dev@lists.osgeo.org> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
-- Ko Nagase (sanak)
Georepublic Japan
mail: geosanak@gmail.com <mailto:geosanak@gmail.com>
nagase@georepublic.co.jp <mailto:nagase@georepublic.co.jp>
All I was trying to say was that during my development of the KSP wrapper I had some memory problems, I resolved them. Before submitting the code. As far as I am aware there are no memory issues with the ksp code.
I was wondering what the memory problems were with the tsp code.
regards
Dave.
Hi Dave,
Sorry, I just started to check new pgRouting 2.0 and its issues,
but, if you use Linux(Ubuntu .etc), it seems that there is no reported issue about ksp memory problems.
So, in that case, could you create a new issue?
Regards,
_______________________________________________
pgrouting-dev mailing list
[pgrouting-dev@lists.osgeo.org](mailto:pgrouting-dev@lists.osgeo.org)
[http://lists.osgeo.org/mailman/listinfo/pgrouting-dev](http://lists.osgeo.org/mailman/listinfo/pgrouting-dev)
My schedule is for the next 2 wks will be focused on some contract work I have to deliver So I’m not sure how much time I will have to tackle pgRouting issues.
I think I can work in looking at the new TSP issues for that starts. My next major pgrouting task is to look at them memory issues that are causing crashes and std::bad_alloc issues. I’m not looking forward to this task because the problems seems to be intermitent and the fact that is works in one setup does not mean that you have solved the problem. I also think this is related to postgresql palloc usage and subtle issues related to that.
If you find specific crashes or issues you should create a new ticket with all the appropriate details on how to reproduce it and in the body of that ticket include '#141' so they are linked.
Thanks,
-Steve
On 6/26/2013 11:06 PM, Stephen Woodbridge wrote:
Hi All,
Dave P. - thanks for the TSP problem reports.
Nagase-san - thank you for the crash reports.
My schedule is for the next 2 wks will be focused on some contract work
I have to deliver So I'm not sure how much time I will have to tackle
pgRouting issues.
I think I can work in looking at the new TSP issues for that starts. My
next major pgrouting task is to look at them memory issues that are
causing crashes and std::bad_alloc issues. I'm not looking forward to
this task because the problems seems to be intermitent and the fact that
is works in one setup does not mean that you have solved the problem. I
also think this is related to postgresql palloc usage and subtle issues
related to that.
I just checked in a few changes related to TSP issues.
1. fixed the order reporting when an end node is specified
2. added checks if less than 4 locations are requested in tsp and report error
3. fixed some other minor bugs I found while review the code
that really needs to be fixed, but I'm not sure how this was intended to work in the first place before I converted it to the new code. I added a bunch of questions to the the ticket. Some feedback would be appreciated.
If you find specific crashes or issues you should create a new ticket
with all the appropriate details on how to reproduce it and in the body
of that ticket include '#141' so they are linked.
Thanks,
-Steve
On 6/26/2013 11:06 PM, Stephen Woodbridge wrote:
Hi All,
Dave P. - thanks for the TSP problem reports.
Nagase-san - thank you for the crash reports.
My schedule is for the next 2 wks will be focused on some contract work
I have to deliver So I'm not sure how much time I will have to tackle
pgRouting issues.
I think I can work in looking at the new TSP issues for that starts. My
next major pgrouting task is to look at them memory issues that are
causing crashes and std::bad_alloc issues. I'm not looking forward to
this task because the problems seems to be intermitent and the fact that
is works in one setup does not mean that you have solved the problem. I
also think this is related to postgresql palloc usage and subtle issues
related to that.