I don’t believe it to be a ADVANCED WOO SEARCH plugin issue at all. We have an enterprise server w/ multiple site installs at WPE. We’re seeing this SAME issue but we do NOT have AWS installed at all. We’re simply using a search form w/ two input fields – one to set up search and two to restrict to post type=product.
WITHOUT the 2nd parameter, if item can’t be found, it sez so w/ a item not found page. WITH the 2nd restriction, if it cant find a product w/ that name, description or tag, it immediately gets a WPE 502 ‘processs taking too long’ error. WPE is saying its accessing memory it shouldn’t and creating a segfault. They’ve suggested a plugin conflict, but this is NOT AWS, not any plugin, just a simple search form. One that degrades/fails acceptably W/O the 2nd parameter, but is getting hijacked by WPE’s rogue application security routines when the 2nd parameter is deployed.
I haven’t found a fix yet either.