#4119 (ok 4.1.0-rc3) Huge session data with $cfg['Error_Handler']['gather']


With $cfg['Error_Handler']['gather'] the session data can get really huge with no real benefit to the user. The problem is that we store full backtrace with all objects passed as parameters.

This means that there are several PMA_Response objects holding whole pages in the session data.

IMHO we should preprocess the backtrace with logic we currently apply getBacktraceDisplay, so that only information we use is stored in the session.


  • Marc Delisle

    Marc Delisle - 2013-11-26

    What is the goal of storing errors in session data?

  • Michal Čihař

    Michal Čihař - 2013-11-27

    The errors need to be stored there to be shown as some requests don't get rendered directly to user. So this is IMHO issue even without enabled $cfg['Error_Handler']['gather'].

    With $cfg['Error_Handler']['gather'] enabled, this get just bigger problem.

    IMHO it was supposed to be used with some error page, which does not exist (and method dispErrorPage is not used anywhere).

  • Marc Delisle

    Marc Delisle - 2013-11-27

    So to improve the situation, I could remove the "gather" option and the dispErrorPage() and dispAllErrors() methods for 4.1.0-rc2.

    Also in __destruct() I could lower the value from 20 to say, 10.

  • Marc Delisle

    Marc Delisle - 2013-11-29
    • assigned_to: Marc Delisle
  • Michal Čihař

    Michal Čihař - 2013-12-02

    I'm okay with all you propose (dropping gather option and dispErrorPage(), dispAllErrors() methods and decreasing limit).

  • Marc Delisle

    Marc Delisle - 2013-12-02
    • summary: Huge session data with $cfg['Error_Handler']['gather'] --> (ok 4.1.0-rc3) Huge session data with $cfg['Error_Handler']['gather']
    • status: open --> resolved
    • Priority: 5 --> 1
  • Marc Delisle

    Marc Delisle - 2013-12-12
    • Status: resolved --> fixed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks