Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

[resolved] error acessing tickets list

Hi,
The error below occurs when I try click in Closed Tickets after I Upgrade from OsTicket 1.6 to 1.8:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 5 bytes) in /home/.../class.osticket.php on line 272

Someone have an idea?

Comments

  • Do you have the correct version of MySQL and mysqli php extension installed?
    that line is from the function logDBError.. it should have produced a stack trace too, do you have that? can you show the apache error logs?
  • This error occurs in the OSTicket body. I haven't access to apache error logs or LogDbError cause I use a free hosting service.
  • Hmm, closed tickets probably tries to use more ram than you are allocated then.
  • I concurr with gizly's assessment because of your statment "I use a free hosting service". :)
  • I am getting the same error... I don't use a free hosting service. Below is the request I submitted to our hosting company and they said it was approved.
    Hello,

    The memory_limit for  ****** has been updated to 128M as requested.

    Regards,
    Dion B.
  • The error was: "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 5 bytes) in /home/.../class.osticket.php on line 272"

    134,217,728 bytes *IS* 128 megabytes.

    It would appear that you are using more than 128 megabytes, so setting your memory limit to 128 megabytes would not alleviate the issue.
      Setting the limit higher than 128mb may have the desired effect.
  • I haven't any problems now I'm using version 1.9.4., yet the environment has no changes.
  • So you haven't changed anything... and now this is working?
  • Yes, everything is working well after I had installed the new version of OSTicket.
  • Okay then.  I will close this thread and mark it resolved.  Please feel free to start a new thread if you have another question, comment, etc.

    solution was: to upgrade to current (1.9.4)
This discussion has been closed.