[pgrouting-dev] TSP, server crashes and what nots

[Dave Potts]

On 27/06/13 09:27, sanak wrote:
Hi Sanak

Perhaps I phrase my comment the wrong way.

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 at pinan.co.uk 
> <mailto:dave.potts at 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 at swoodbridge.com
>>     <mailto:woodbri at 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 at lists.osgeo.org
>>         <mailto:pgrouting-dev at lists.osgeo.org>
>>         http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>>
>>
>>
>>
>>     -- 
>>     Ko Nagase (sanak)
>>     Georepublic Japan
>>     mail: geosanak at gmail.com <mailto:geosanak at gmail.com>
>>     nagase at georepublic.co.jp <mailto:nagase at georepublic.co.jp>
>>
>>
>>     _______________________________________________
>>     pgrouting-dev mailing list
>>     pgrouting-dev at lists.osgeo.org  <mailto:pgrouting-dev at lists.osgeo.org>
>>     http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
>     _______________________________________________
>     pgrouting-dev mailing list
>     pgrouting-dev at lists.osgeo.org <mailto:pgrouting-dev at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
>
>
> -- 
> Ko Nagase (sanak)
> Georepublic Japan
> mail: geosanak at gmail.com <mailto:geosanak at gmail.com>
> nagase at georepublic.co.jp <mailto:nagase at georepublic.co.jp>
>
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20130627/2dc729aa/attachment-0001.html>