0006591: ADODB / Memory Issue / etc? - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0006591	mantisbt	administration	public	2006-01-14 19:15	2007-08-02 02:31

Reporter	mickoz	Assigned To	grangeway
Priority	normal	Severity	crash	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	0.19.4

Summary	0006591: ADODB / Memory Issue / etc?
Description	Fatal error: Call to undefined method ADORecordSet_mysql::RecordCount() in /.../mantis/core/database_api.php on line 122 When I go in view_all_bug_page.php (i.e. View Issue) I keep getting that error. I just upgraded from 0.18.2 to 0.19.4. -- MySQL Server version: 4.1.15 -- PHP Version: 5.0.5 I upgraded because current version wasn't able to work with PHP 5. And the change I needed is in the 0.19.1 version of mantis: 0004745: [other] PHP 5 array_merge() change causes errors (vboctor) However, there was a lot of other change... I had a lot of problem upgrading... having that error and some memory size problem too. All I did initially was boost memory with ini_set("memory_limit","32M"); (and also renamed the directory, but I am not sure that is an issue) and then I could upgrade. I also saw the memory limit issue when I tried to push upgrade, when there was no more upgrade on the list, but I cannot reproduce for now. Is there a know reason for this, because if it is know, I don't want to spent hour to figure out why it behave like that!? I just was able to get view_all_bug_page.php "working" that is if I output something before using it (in my config file, I have enabled notice and generated a notice to see if I could not find other error, and then the view_all_bug_page.php seem to work). However, I then get often error like this: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 142429069 bytes) in /.../mantis/core/adodb/adodb.inc.php on line 3289 And no we don't have much bugnote... hundreds at maximum... That seem very high as demand... is there something wrong happening? I don't feel very good to use that last stable release. I might consider to redowngrade and re-update to the most recent 0.18.x (that might resolve my issue and avoid problem like this?). However, like stated at first, the issue that got me to upgrade... was fixed in 0.19.1 Any idea on the issue? I am not even confident the upgrade really went well with that issue :S Yes I have found similar page: http://bugs.mantisbt.org/view.php?id=4545 http://bugs.mantisbt.org/view.php?id=4798 However they are not exactly the same, but I suspect they are similar problem. That seem pretty major... :/
Tags	No tags attached.

grangeway 2007-07-16 14:38 reporter ~0015057	Thank you for taking the time to report a problem with mantis. Since this problem report was originally made, a number of releases have occured - some of which included performance fixes from myself/others. It appears that this issue has either been fixed, or may not be a relevant report for the current release. Please download the latest release from http://www.mantisbt.org/download.php [^] [^] If you are able to reproduce this bug in the current release, or have some more information on how this feature could be improved in the current release. Please either change the mantis version on this bug report to the version you tested and change the status back to "Open", or open a new issue report wit more information. Again, thank you for your continued support and report. Paul