Mantis Bugtracker          
testlink.org

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007178TestLinkTest Specification Importpublic2015-06-26 11:522019-01-19 15:08
Reporterschoenrock 
Assigned Tofman 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionunable to reproduce 
PlatformOSOS Version
Product Version1.9.13 (2015 #1) 
Fixed in Version 
Summary0007178: LATEST GITHUB CODE - The update of already imported test cases results in an fatal error by using a file size > 1.300.000 bytes.
DescriptionWe have an xml file with the size 1.309.364 (370 individual test cases) bytes.
The xml file is already imported in test specification area.
After we had modified the xml file we want to import the file again to edit the already existing test cases.
If we try this we get the following fatal error.

"Fatal error: Allowed memory size of 155189248 bytes exhausted (tried to allocate 32 bytes) in /srv/www/htdocs/testlink/1.9.13.2/third_party/adodb/adodb.inc.php on line 2967 "

We try the same steps with an xml files which have the size 1.109.460 bytes (347 individual test cases) and in this case everything works correctly.
Steps To ReproducePreconditions:
1. Create a xml file with a size > 1.300.00 bytes
2. Import this xml file in the test specification area.

Steps:
 1. Export the test cases from this suite to an XML file: "Test Case Operations / Export"
 2. Edit the XML file and change the action or expected result
 3. Select the option to import test cases to the same suite: "Test Case Operations / Import"
 4. Choose the previously edited file and select "Has same name" and "Update data on latest version" options.
 5. Select "Upload file" option
 6. on the right side you see the following output:
    "Fatal error: Allowed memory size of 155189248 bytes exhausted (tried to allocate 32 bytes) in /srv/www/htdocs/testlink/1.9.13.2/third_party/adodb/adodb.inc.php on line 2967 "
TagsNo tags attached.
Database (MySQL,Postgres,etc)mysql 5.5.40-0+wheezy1
Browser
PHP Version
TestCaseID
QA Team - Task Workflow Status
Attached Filesxml file icon 3072-SPACE-SHUTTLE.testproject-deep.xml [^] (1,620,809 bytes) 2015-06-26 20:00
? file icon php.ini [^] (69,229 bytes) 2015-06-26 20:03
xml file icon RB.xml [^] (1,309,364 bytes) 2015-06-29 10:23

- Relationships
related to 0007484closedfman Not able to add all the required test cases to the test plan. 

-  Notes
(0023556)
fman (administrator)
2015-06-26 13:46

for import issue the sample file is needed always.
(0023561)
fman (administrator)
2015-06-26 20:00

just tested with attached file, that has test cases without custom fields, without keywords, without requirements, and that are empty.
attached also php.ini
tested on MacBookAir with 4GB RAM.
(0023568)
schoenrock (reporter)
2015-06-29 12:39

Thanks for the php.ini file it was very helpful for us.
The difference between our and your php.ini is the memory_limit.
Yours set to 1GB and ours to 148MB (php default 128MB).
Increasing the memory limit solves the problem. We set it to 256MB.
Setting to 1GB in the productive system is not accaptable for us, because it could result in memory problems.

Setting mem limit to 256MB is ok, but I hope we didn't have to increase it anymore.

In our php apps we had similar problems - we solve the "big data -> lot's of memory" problem with slicing the data into parts and evaluate the parts instead of whole data at once.
But that wasn't always easy to implement.

I think you can close this issue with the advice to the mem_limit.
Perhaps you can add a note in the installation manual.

thanks :-)
(0023571)
fman (administrator)
2015-06-29 18:34
edited on: 2015-06-29 18:34

It would be great if you can do test with larger files, because when trying to test this I've hit a different issue that IMHO is related to a time out.
Have generated using 3072-SPACE-SHUTTLE.testproject-deep.xml and doing copies, a test project with 5000 test cases, that when exported generates a 2.7 MB file (in my env takes 4 minutes), then TestLink blocked with message server closed connection without sending data


any help will be welcomed


- Issue History
Date Modified Username Field Change
2015-06-26 11:52 schoenrock New Issue
2015-06-26 13:46 fman Note Added: 0023556
2015-06-26 13:47 fman Assigned To => fman
2015-06-26 13:47 fman Status new => feedback
2015-06-26 20:00 fman Note Added: 0023561
2015-06-26 20:00 fman File Added: 3072-SPACE-SHUTTLE.testproject-deep.xml
2015-06-26 20:03 fman File Added: php.ini
2015-06-29 10:23 schoenrock File Added: RB.xml
2015-06-29 12:39 schoenrock Note Added: 0023568
2015-06-29 12:39 schoenrock Status feedback => assigned
2015-06-29 18:34 fman Note Added: 0023571
2015-06-29 18:34 fman Note Edited: 0023571 View Revisions
2015-06-29 18:35 fman Status assigned => feedback
2016-03-28 09:25 fman Relationship added related to 0007484
2019-01-19 15:08 fman Status feedback => resolved
2019-01-19 15:08 fman Resolution open => unable to reproduce



Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker