The segefault is caused by repeated calls to start and stop the gtk main_loop in a single python process. WebKit does not like the repeated start and stops in main_loop, maybe because some state is left behind.
The test browser is stable called repeatedly in a subprocess. This is slower than working the browser in proc.
The segefault is caused by repeated calls to start and stop the gtk main_loop in a single python process. WebKit does not like the repeated start and stops in main_loop, maybe because some state is left behind.
The test browser is stable called repeatedly in a subprocess. This is slower than working the browser in proc.