View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Fatal error: Allowed memory size of 67108864 bytes exhausted - ProjeQtOr
 

Fatal error: Allowed memory size of 67108864 bytes exhausted

More
29 Mar 2012 11:02 #1 by climb4fun
Hi Babynus,


applying report "work plan per week", I get following error message:
"Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 32 bytes) in /users/climb4fun/www/projector/tool/projector.php on line 1037"


It happens only on a project which has a lot of real work records. On smaller projects it works well. Report "work plan per month" works fine as well.


LogFile out of my test environment
2012-03-29 10:30:39 ===== TRACE ===== NEW CONNECTED USER 'klaus'
2012-03-29 10:30:44 ===== TRACE ===== cron started at 29/03/2012 10:30:44
2012-03-29 10:31:05 ***** ERROR ***** ERROR *****
2012-03-29 10:31:05 ***** ERROR ***** on file '/users/climb4fun/www/projector/model/IndicatorValue.php' at line (234)
2012-03-29 10:31:05 ***** ERROR ***** cause = Trying to get property of non-object
2012-03-29 10:38:04 ===== TRACE ===== DISCONNECTED USER 'Klaus'
2012-03-29 10:48:49 ===== TRACE ===== NEW CONNECTED USER 'klaus'
2012-03-29 10:48:53 ===== TRACE ===== cron started at 29/03/2012 10:48:53
2012-03-29 10:49:13 ***** ERROR ***** ERROR *****
2012-03-29 10:49:13 ***** ERROR ***** on file '/users/climb4fun/www/projector/model/IndicatorValue.php' at line (234)
2012-03-29 10:49:13 ***** ERROR ***** cause = Trying to get property of non-object
2012-03-29 10:53:28 ***** ERROR ***** Error on SqlElement to get 'idBill' for Class 'PlannedWork'  : field 'idBill' not found in Database.
2012-03-29 10:53:28 ***** ERROR ***** Error on SqlElement to get 'idBill' for Class 'PlannedWork'  : field 'idBill' not found in Database.


Version 2.0.1


Klaus

Please Log in or Create an account to join the conversation.

More
29 Mar 2012 12:27 #2 by babynus
The default memory limit of your PHP server is 64M.
It is very few for a productive server.
I'll have a look on improvement of this report, but I must advise you to increase this limit (at least double it) otherwise you may reguliarly face this king of issue.

Regards.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
29 Mar 2012 12:52 #3 by babynus
I had a look at the report : there is not much to optimse.
This report is not at all the more complex or memory loading report.

Do you reproduce the issue every time, or did you face it on a given context ?
(maybe another user was using a memory consiming process, such as pdf export, while you ran this report...)

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
29 Mar 2012 16:02 #4 by climb4fun
First I checked memory limit:
In my test environment I have 64M memory limit.


In my productiv enviroment it's much more memory. I discovered, error message in my productiv environment is different:
If I didn't select a project and run report with wildcard then message is:
Fatal error: Maximum execution time of 30 seconds exceeded in /opt/lampp/htdocs/projector/report/globalWorkPlanning.php on line 76
If I select the project with most entries, then message is
Fatal error: Maximum execution time of 30 seconds exceeded in /opt/lampp/htdocs/projector/tool/projector.php on line 1261


Klaus

Please Log in or Create an account to join the conversation.

More
29 Mar 2012 17:57 #5 by babynus
Hi,
I understand better...


The two errors you logged are the same : time limit (timeout reached).
I'll have a look.
What is surprising is that it occurs only on this report ... or do you reproduce this issue on any other report ?


I'll try and increase Timeout at runtime for every report...
I'll also have a look at indexes in the database : as there is only one request, I don't really explain such a long time running.


Regards.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
30 Mar 2012 06:58 #6 by climb4fun
I did observe this error only on running report "work plan per week" with wildcard and running report for project with a lot of entries.

Please Log in or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.043 seconds

Cookies settings

×

Functional Cookies

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Please login to see yours activities!

Other cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.