Wow that are alot of replys :-) Anyway i am using version: 1.9.5
And before everybody starts screaming about that, this project was handed to me and i knew (know even) nothing about zend framework. I meant a trace file but i also got an cachegrind file which is about 170mb big... I did an edit of php.ini to 512 mb but this still generates the problem. I am not using an mssql database but i do use the excel generator. But this is used on different parts of the application. I dont think that it has anything to do with it. I tried to use the " https://gist.github.com/628803 helper script for analyzing the output of a PHP xdebug code trace " But it outputs nothing :-( [root@web01 tmp]# php trace.php trace.2043925204.xt memory-own 20 PHP Warning: Module 'xdebug' already loaded in Unknown on line 0 parsing... ( 2.26%) ( 5.12%) ( 7.54%) ( 9.95%) (12.37%) (14.78%) (17.20%) (19.62%) (22.03%) (24.45%) (26.86%) (29.28%) (31.70%) (34.11%) (36.53%) (38.94%) (41.36%) (43.78%) (46.19%) (48.61%) (51.03%) (53.44%) (55.86%) (58.27%) (60.69%) Done. Showing the 20 most costly calls sorted by 'memory-own'. Inclusive Own function#calls time memory time memory ------------------------------------------------ [root@web01 tmp]# So what steps do i need to take? I think that i have written something that fills the global variable ($this) with alot of stuff, but well how do i hunt it down? -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Allowed-memory-size-exhausted-tp3701480p3703294.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
