Re: [pmapper-users] Legend - Segmentation fault
Thanx a lot for the explanation. legendDynamicUpdate0/legendDynamicUpdate which is anyway the default, so you probably have set this to 1. I guess it works only with Mapserver 6.+. Good guess! Indeed, if it set it back to 0 the segfault doesn't show up anymore! : ) I had noticed some layers not being mentioned in the dynamic legend anyway, so I think I better not use it. Of course, now that makes a really big legend to scroll down. I will see how I can tune it best. Thanx again! Chris On Wed, Feb 20, 2013 at 11:38 PM, Armin Burger armin.bur...@gmail.comwrote: segfaults of Apache caused by PHP Mapscript are a bit outside the scope of p.mapper... Since the refactoring of all the PHP Mapscript code in MS 6, the amount of irregularly appearing and difficult to trace segfaults has increased dramatically. That was for me the reason to e.g. rewrite some WMS handling in PHP Mapscript again in Python Mapscript, which however doesn't help you in this case... To avoid legend updates based on visible features of the map you can deactivate it by setting legendDynamicUpdate0/legendDynamicUpdate which is anyway the default, so you probably have set this to 1. I guess it works only with Mapserver 6.+. For larger amounts of active layers with higher numbers of features displayed it should get quite slow since it needs to run all loops through layer features in PHP. Having this inside a C function called via Mapscript should be really fast (the map rendering is using the same type of checks, and it is fast), but this has never made its way to Mapserver code. Armin On 02/20/2013 11:27 AM, Chris forum wrote: Hi all, pmapper 4.3 mapserver 6.2 php 5.3.3-7 Debian server I just noticed the following Apache notice in the error log: [notice] child pid 489 exit signal Segmentation fault (11) It happens when I pan the map while the legend tab (swap as in Plainlayout4) is displayed. With each pan several notice appear with an incremental pid. I thought there was one faulty layer, but I can not point one out after several tests. Could it be that there are too many layers displayed and the legend mechanism can not cope with it? Regards, Chris -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
[pmapper-users] Legend - Segmentation fault
Hi all, pmapper 4.3 mapserver 6.2 php 5.3.3-7 Debian server I just noticed the following Apache notice in the error log: [notice] child pid 489 exit signal Segmentation fault (11) It happens when I pan the map while the legend tab (swap as in Plainlayout4) is displayed. With each pan several notice appear with an incremental pid. I thought there was one faulty layer, but I can not point one out after several tests. Could it be that there are too many layers displayed and the legend mechanism can not cope with it? Regards, Chris -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
Re: [pmapper-users] Legend - Segmentation fault
segfaults of Apache caused by PHP Mapscript are a bit outside the scope of p.mapper... Since the refactoring of all the PHP Mapscript code in MS 6, the amount of irregularly appearing and difficult to trace segfaults has increased dramatically. That was for me the reason to e.g. rewrite some WMS handling in PHP Mapscript again in Python Mapscript, which however doesn't help you in this case... To avoid legend updates based on visible features of the map you can deactivate it by setting legendDynamicUpdate0/legendDynamicUpdate which is anyway the default, so you probably have set this to 1. I guess it works only with Mapserver 6.+. For larger amounts of active layers with higher numbers of features displayed it should get quite slow since it needs to run all loops through layer features in PHP. Having this inside a C function called via Mapscript should be really fast (the map rendering is using the same type of checks, and it is fast), but this has never made its way to Mapserver code. Armin On 02/20/2013 11:27 AM, Chris forum wrote: Hi all, pmapper 4.3 mapserver 6.2 php 5.3.3-7 Debian server I just noticed the following Apache notice in the error log: [notice] child pid 489 exit signal Segmentation fault (11) It happens when I pan the map while the legend tab (swap as in Plainlayout4) is displayed. With each pan several notice appear with an incremental pid. I thought there was one faulty layer, but I can not point one out after several tests. Could it be that there are too many layers displayed and the legend mechanism can not cope with it? Regards, Chris -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
