Symfony ContextErrorException : unserialize Error at offset (DataCollector) - Error 500 when debug enabled

[ghost]

Describe the bug

Error 500 when debug enabled php 7.3.25, if i use php 7.2 no error

Steps to Reproduce

1. Make a new installation.

2. Enable Debug Mode

3. Use php 7.3.25

4. Go to the orders list (look at the error)

5. Go to the customers list (look at the error)

6. Go to the categorys list (look at the error)

7. Now go to the product list there are no error

Configuration

I use a server with Plesk on debian

Error in console Tab

Error in Network Tab

A lot of memory

Additional information

I found a similar issue #16873

I don't have this error on all new controller.

CRITICAL00:53:28 | php | Uncaught Notice: unserialize(): Error at offset 315894 of 1800983 bytes
-- | -- | --
CRITICAL00:53:28 | request | Uncaught PHP Exception Symfony\Component\Debug\Exception\ContextErrorException: "Notice: unserialize(): Error at offset 315894 of 1800983 bytes" at /var/www/vhosts/ee.wtf/httpdocs/1770/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/DataCollector/DataCollector.php line 56

• PrestaShop version: 1.7.7.0
• PHP version: 7.3.25

[matks]

Hi @okom3pom so you have multiple different issues here 😄

• the JS error is because you are GDPR module V1.2.0 which is not compatible with PS 1.7.7.0 ; you need the v1.2.1
• the HTTP 500 issue I dont know, we need more infos
• the Uncaught Notice: unserialize(): Error at offset 315894 of 1800983 bytes is Symfony debug tools trying to serialize your data to present them into the Symfony Debug bar and failing because you have too much data 😄

[ghost]

Hi @matks for the js i open an other issue : #22232

The error 500 is only when i use php 7.3

[ghost]

I work on a new install

[florine2623]

Hi @okom3pom & @matks ,
I did manage to reproduce the same issue on PS 1.7.7.0 fresh install + PHP 7.3 + debug mode ON.

Debug mode OFF, no error 500 :

Debug mode ON :

I’ll add this to the debug backlog so that it’s fixed.
If you have already fixed it on your end or if you think you can do it, please do send us a pull request!
Thanks.

[ghost]

Hi @florine2623 i think it's a migration page problem not only in the order page, the label migration is better?

And i don't understand why I haven't seen this when i tested the beta and RC

I try on a RC when i have the time

[florine2623]

@okom3pom I will add migration label also, thanks!

I have tested this on beta1, beta2 and RC1, I have the same issue on the three fresh installs : PHP 7.3 + debug ON = error 500

Please see the screenshots below :
beta1 :

beta2 :

RC1 :

The issue is present on the 3 previous versions.
Also, when clicking on the web profiler, here's the error :

[marionf]

@hibatallahAouadni Could you check if it's a regression ?

[khouloudbelguith]

Hi @marionf, @hibatallahAouadni,

The PS1.7.6.9 is not compatible with PHP7.3.

Thanks!

[matks]

Hi, from what I see in the screenshots there is 2 issues:

1. the JS error is this one BO - Error in console in order page  #18776 it is fixed when using GDPR module v1.2.1

2. the HTTP 500 error you can see being displayed in the Console is Symfony Debug Bar that crashes because it tries to serialize an object too big and it crashes (not enough memory). This can happen with big orders data, but it's not an issue.

It's not an issue because it's just Symfony debug tool trying to compute some data to help the developer but the data is too big 😄 . Symfony is just too hungry and tries to process a data too big for it, nothing bad about that. The only consequence is that the request fail and the SF debug bar does not appear in debug mode.

[ghost]

Hi,

@matks i know 1.2.1 fix the JS error but the issue is :

#22232

If prestashop don't propose update i don't think merchant goes download zip from github and install the zip manualy .

This issue concern only the 500 in the Console.

[matks]

I update the title to make it more accurate.

[hibatallahAouadni]

Hello @marionf

As @khouloudbelguith mentioned above, it couldn't be a regression cause 1.7.6.9 is not compatible with 7.3.
So, I change the status to To Do, feel free to change it 😅

Thanks!

[ghost]

I complete the Issue with :

Make a new installation.

Go to the orders list (look at the error)

Go to the customers list (look at the error)

Go to the categorys list (look at the error)

Now go to the product list there are no error

@matks say :

It's not an issue because it's just Symfony debug tool trying to compute some data to help the developer but the data is too big

But a lot of listing give an error and not a lot of datas

[Progi1984]

Fixed by #22688