I am using laravel/homestead (virtualbox, 6.4.0) which is Ubuntu 18.04. Linux nxtboard 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Here are the requested log files. Let me know if you need more information.
I’m using the 64 bit version of PHP and when I followed the install instructions from your site, I downloaded the 64bit version of PDFTron as well.
Still getting the crash. Here is a debug file I generated using apport-bug. I’m not sure where else there would be other diagnostic info since it’s being run on the cli.
It did and I also figured out the problem I had was not setting the full path to the shared library in the ini file for PDFNet so that I didn’t have to enable the dynamic library setting. What’s odd about that to me is that if you look at how other ini files are setup, they don’t list the directory either.
However I have noticed that with running the full set of samples, I am still seeing seg faults for a number of other samples(even with enable_dl on and the removal of the ini file). Do you see this as well?
Hey there, I notice this is from June. But has the team narrowed down the segfault issue when exiting?
It returns a Segmentation fault only when the process hasn’t made any writes. But honestly I’m trying to find where the error is coming from so I can wrap it to throw a proper PHP exception. And at least know nothing has been written.
I believe the segfault on application termination is still there yes.
Since the application is terminating and all resources are being released anyway, could you elaborate on why you are trying to throw a proper exception?
If the app is terminating why is catching important?
Note, that a process cannot continue to run after a seg fault, the process needs to end, you are only supposed to get any last diagnostic info before allowing the process to terminate.