VirtueMart Forum

VirtueMart 2 + 3 + 4 => General Questions => Topic started by: melsonmarketing on February 04, 2019, 16:30:42 PM

Title: Macbook crashes server
Post by: melsonmarketing on February 04, 2019, 16:30:42 PM
Hi!

I'm facing a very strange error.

VirtueMart 3.4.2
J! 3.9.2
Php 7.2.6

Working on the VM administration with Win10 /Firefox causes no problems

As soon as a Macbook (IOS 10.14.2) is used by the customer thge site freezes AND overloads the server.

In the server errorlogs we fell over this, as it's a massive request that it repeats itself:

ROOT/components/com_virtuemart/assets/css/chosen.css?vmver=7a8830ef

As written above: Tested from several machines with different browsers without problems - no problem with browserlink either.

It ONLY happens with this one machine.

All categorychoosers and dropdowns (filters) are loading in an endless loop

Any ideas?

Thanks for any tipp!

Regards
Michael

Title: Re: Macbook crashes server
Post by: AH on February 04, 2019, 17:37:41 PM
Try turning off

"Enable VirtueMart 404 error handling "

In VM administration configuration
Title: Re: Macbook crashes server
Post by: melsonmarketing on February 04, 2019, 22:39:21 PM
Thank you - that seems to work.

Do you have any details about this issue?

I mean I changed a systemsetting that should affect each user agent. In most cases the system would crash the browser  - but here it is vice versa: a single user crashes the server. The php memory limit is set to 256 MB, max execution to 900.

Really strange but:

Thanks a lot!

:o   ;D
Title: Re: Macbook crashes server
Post by: jenkinhill on February 04, 2019, 23:30:18 PM
See http://forum.virtuemart.net/index.php?topic=141213.0
http://forum.virtuemart.net/index.php?topic=141220
Title: Re: Macbook crashes server
Post by: melsonmarketing on February 05, 2019, 10:01:47 AM
Okay, disabling the 404 error-handling finally did the trick.

Thanks jankinhill for the links - I didn't see them before.

Title: Re: Macbook crashes server
Post by: AH on February 05, 2019, 12:21:53 PM
This will be fixed in the latest release - but for now - disabling VM 404 handling is the solution