PHP Fatal error on company deatils update

alex611

I am using Group filter to get specific companies listed, which i need to edit.

While -without filter- i can edit and save changes, once i apply a Group filter (actually ANY filter) changes to company details are not saved. Nothing happans when hitting "save"

Instead i have a error in my error logs:
PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 4359633 bytes) in C:\\wwwmap\\epesi\\include\\error.php on line 131, referer: ~~[url=http://www.xx.com/epesi/]~~http://www.xx.com/epesi/[/url]

Trying to increase in .htaccess allowed_memory to 128M breaks the whole layout (colorless grid tables)

This issue is ONLY when i apply filters and try to directly jump to "edit company details".

php_flag magic_quotes_gpc are OFF
Running on Windows 2008 machine with Apache (not IIS)

Your help is appreciated

alex611

Strange, i tried from 3 different server locations, different browsers... always same issue.
Today, one of my colleagues tried on his pc without issue.

I need a hint where to look. something i miss here.

ethnar

Hello,

The one idea I have right now is the amount of records displayed per page. If you use 50 records/page, in certain server configurations you can experience memory issues. Please try with 15/25 records.
If that's not the amount of records, I'd suggest comparing yours and your colleague User Settings and permissions.

How many Companies do you have total? Did you add some fields to be displayed in table view?

Also - increasing memory limit in .htaccess shouldn't cause the css not to load. It must be some underneath issue that's actually causing it.

Kind regards,
Arek

alex611

Hello Arek,

you are a genius :wink:
That was it. My colleague worked in a 25 per page displays, while i was using 50 per page, which probably caused the crash in memory.
Yes, i added also additional views in grid, with a total of 1450 companies in database.

Reducing to 25 per page views did the trick.. and works fine so far.
Hope that you guys find a fix in next releases, as it is annoying issue, very difficult to think about that such a simple detail can fix the trouble.

Thank you very much for pointing out, you guys have a great support. I appreciate

regards
Dimi

ethnar

Hello,

I'm glad you have a way to deal with this issue.

As for permanently fixing it - I can't really promise anything here. Such error is strictly related to the server configuration and thus far, on all our servers we didn't encounter it. The reason I knew this might be an issue is because one of epesi users contacted us about similar issue a while ago, but I could only investigate it briefly, enough to notice that 50 records/page is what's causing the issue.

I'll see if there's anything we can do to resolve that issue, but again, I can't promise anything.

I apologize for inconveniences it may be causing.

Kind regards,
Arek

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge