Adam Zieliński
Adam Zieliński
I was still able to trigger the crash even with HPOS disabled.
I built PHP with `-g2 -O0` and couldn't reproduce the issue anymore. Weird!
I managed to get some unminified error information:  
The `woocommerce-extra-checkout-fields-for-brazil` lives at https://github.com/claudiosanches/woocommerce-extra-checkout-fields-for-brazil/
The crash also happens without the `woocommerce-extra-checkout-fields-for-brazil` plugin.
I couldn't reproduce it on vanilla `woocommerce`, too, which makes me think it's related to the `pagbank-connect` plugin. Also noteworthy, `post_message_to_js` used by the `fetch()` HTTP transport showed up in...
Here's a different stacktrace I got with vanilla WooCommerce, likely related to an out of memory error: ``` Uncaught RangeError: Maximum call stack size exceeded at runtime.asm. (wasm-error-reporting.ts:60:14) at invoke_viii...
Ricardo said: > I see the Pagbank plugin has an issue with the CORS. Meaning that the backend calls doesn’t work when called with fetch/frontend ajax calls. Probably it is...
> I managed to get some unminified error information: > >  ![CleanShot 2024-01-22 at 18 19 16@2x] This error was fixed by @bgrgicak in...
@bgrgicak nothing more than what I described in other comments – install those plugins, browse for a prolonged period of time, hope the crash happens.