changed the max_execution_time to 160 :-)
( ! ) Fatal error: Maximum execution time of 160 seconds exceeded in
/home/aghaffar/mantisbt/core/user_api.php on line *988* Call Stack #Time
MemoryFunctionLocation 10.001292036{main}( )../my_view_page.php*:*0 210.1821
67351312user_get_assigned_open_bug_count( )../my_view_page.php*:*95 310.1822
67351312helper_project_specific_where( )../user_api.php*:*1007 410.1823
67351312user_get_all_accessible_projects( )../helper_api.php*:*296 5163.6350
72551796array_merge <http://www.php.net/array_merge> ( )../user_api.php*:*
988
On Sat, Apr 18, 2009 at 4:20 AM, Atif Ghaffar <[email protected]>wrote:
> change the memory_limit to 160M
>
> Now I get the following error:
> ( ! ) Fatal error: Maximum execution time of 30 seconds exceeded in
> /home/aghaffar/mantisbt/core/user_api.php on line *988* Call Stack #Time
> MemoryFunction Location 10.001192036{main}( ) ../my_view_page.php*:*0 2
> 10.839367351312user_get_assigned_open_bug_count( ) ../my_view_page.php*:*
> 95 310.839467351312helper_project_specific_where( ) ../user_api.php*:*1007
> 410.839467351312user_get_all_accessible_projects( ) ../helper_api.php*:*
> 296 530.268672551796array_merge <http://www.php.net/array_merge> ( )
> ../user_api.php*:*988
>
>
> On Sat, Apr 18, 2009 at 3:59 AM, Atif Ghaffar <[email protected]>wrote:
>
>> Also, i'd be interested to know if removing the call to
>>> project_cache_all at the end of core.php has any noticeable effect on the
>>> mantis installation with your workload.
>>>
>> After the previous failures, I have comment the project_cache_all in
>> core.php
>>
>> Now atleast I get the xdebug error
>> ( ! ) Fatal error: Allowed memory size of 16777216 bytes exhausted (tried
>> to allocate 131072 bytes) in
>> /home/aghaffar/mantisbt/core/project_hierarchy_api.php on line *146
>>
>>
>> *
>> continuing on further disections now
>>
>
>
>
> --
> best regards
> Atif Ghaffar
>
--
best regards
Atif Ghaffar
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
mantisbt-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mantisbt-help