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 - ProjeQtOr
 
 

Fatal error: Allowed memory size

More
25 Sep 2015 21:18 - 25 Sep 2015 21:19 #1 by treddy_karra
Hello

When I opened the link it came up with an error and when I lookup the line in Sql.php, there is only 377 lines of code but the error is referring to 1579. What's wrong with it?

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65488 bytes) in C:\xampp\htdocs\projects\model\persistence\Sql.php on line 1579

Please advise.

Thanks
Thirumal
Last edit: 25 Sep 2015 21:19 by treddy_karra.

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

More
26 Sep 2015 12:43 #2 by babynus
A "memory size" error will reproduce not always on same point.

When I opened the link

What did you do ?
Could you delail use case leading to error ?

Babynus
Administrator of ProjeQtOr web site

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

More
01 Oct 2015 16:43 #3 by treddy_karra
This error throws at the same point every time when you open the login page.

Thanks
Thirumal

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

More
03 Oct 2015 11:24 #4 by babynus
It is really weird.
The default 128MB memory is large enough for all scripts (it may just be too small to convert big reports to PDF)
One option is to try and disable not used PHP extension.
For instance XDebug can consume memory.

I searched and found that line number 1579 can be line in calling script.
I found /model/persistence/SqlElement.php with line 1579 :
$result = Sql::query($query);
so it's a very good candidate for source of issue.
What you can do, to try and find hints, is activate some specific debugging mode : add in your parameters.php file a new parameter :
$debugQuery=true;
Test again and post log file.

Babynus
Administrator of ProjeQtOr web site

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

More
16 Jan 2016 08:48 #5 by jck1307
Hello,
I have the exact same error. I already had a functioning installation with wordpress on my server and I tried to add projeqtor on it.

Where I have to set the $debugQuery=true; instruction in parameters.php?

I put it just after scriptlog instruction but I haven't more information in error.log

require_once "../tool/projeqtor.php";^M
scriptLog(' ->/view/parameter.php');^M
^M
$debugQuery=true;

Thanks for your help,

JC

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

More
17 Jan 2016 11:24 - 17 Jan 2016 11:26 #6 by babynus
Hi,

It is not is the /view/parameter.php wich is the screen (in /view) that displays parameters (user and global parameters).
I now realize that name is ambigous...

It is in the parameters.php (with an s) that contains your parameter (db infos, log infos).
Default location is /files/config/parameters.php, but you may (and should) have changed is on install.
You'll retreive the location of this file (if you don't remember where you moved it) in /tool/parametersLocation.php : it contains one only line with definition of location of parameters file
$parametersLocation = '../files/config/parameters.php'; // This is the default location

In the parameters.php fiel, you'll find location and name of your log file. Default is :
$logFile='../files/logs/projeqtor_${date}.log';
You can add $debugQuery=true; just after this line.

Babynus
Administrator of ProjeQtOr web site
Last edit: 17 Jan 2016 11:26 by babynus.

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

Moderators: babynusprotion
Time to create page: 0.034 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.