php5-fpm crashed with SIGSEGV in munmap()

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

Once you have replied, please change the bug status back to New.

Thanks!

I have attached very detailed crash report - see #1 , it contains a lot of useful debugging information - stack trace , coredump, library dump, memory dump and many further information.

Answer to questions:
1. the specific steps or actions you took that caused you to encounter the problem,
no specific steps or actions from my side at all.

2. the behavior you expected, and
I am expecting not to crash.

3. the behavior you actually encountered (in as much detail as possible).
crash every time after login to OS instance.

It looks like this bug is corresponding with:
https://bugs.php.net/bug.php?id=62886

grep -i fpm /var/log/syslog
Jan 23 20:10:50 PCEUBU1 kernel: [ 36.756379] php5-fpm[6296]: segfault at 7f003725c9a0 ip 00007f004c3788e4 sp 00007fff1d38d670 error 4 in ld-2.15.so[7f004c369000+22000]
Jan 26 13:25:14 PCEUBU1 kernel: [ 74.141373] php5-fpm[6310]: segfault at 7fc380060df8 ip 00007fc39b238934 sp 00007fffb7c92240 error 4 in ld-2.15.so[7fc39b229000+22000]
Jan 29 16:09:23 PCEUBU1 kernel: [ 44.475395] php5-fpm[6384]: segfault at 7f1b9e928528 ip 00007f1bb96f8934 sp 00007fff01302ec0 error 4 in ld-2.15.so[7f1bb96e9000+22000]
Jan 29 17:07:51 PCEUBU1 kernel: [ 39.556787] php5-fpm[6273]: segfault at 7fa95d5f48c0 ip 00007fa975caa934 sp 00007ffffc0f8130 error 4 in ld-2.15.so[7fa975c9b000+22000]
Jan 29 17:37:38 PCEUBU1 kernel: [ 39.217636] php5-fpm[6287]: segfault at 7f85a7dec528 ip 00007f85c2bbc934 sp 00007fffecd20e40 error 4 in ld-2.15.so[7f85c2bad000+22000]
Jan 29 19:58:46 PCEUBU1 kernel: [ 36.124594] php5-fpm[6371]: segfault at 7f5ff9f53528 ip 00007f6014d23934 sp 00007fffb2d5dec0 error 4 in ld-2.15.so[7f6014d14000+22000]
Jan 30 09:21:49 PCEUBU1 kernel: [ 39.105893] php5-fpm[6263]: segfault at 7ffaebbb6528 ip 00007ffb06986934 sp 00007fff6ec342c0 error 4 in ld-2.15.so[7ffb06977000+22000]
Jan 30 09:55:24 PCEUBU1 kernel: [ 39.084566] php5-fpm[6434]: segfault at 7f24763fc8c0 ip 00007f248eab2934 sp 00007fffc45c8c30 error 4 in ld-2.15.so[7f248eaa3000+22000]
Jan 31 09:54:55 PCEUBU1 kernel: [ 39.720127] php5-fpm[6300]: segfault at 7f0030b96528 ip 00007f004b966934 sp 00007fff3f413900 error 4 in ld-2.15.so[7f004b957000+22000]
Feb 4 09:30:40 PCEUBU1 kernel: [ 49.983369] php5-fpm[6424]: segfault at 7fcf9aad98c0 ip 00007fcfb318f934 sp 00007fff7cd3bdf0 error 4 in ld-2.15.so[7fcfb3180000+22000]
Feb 6 10:03:41 PCEUBU1 kernel: [ 40.081709] php5-fpm[6380]: segfault at 7f07de2df8c0 ip 00007f07f6995934 sp 00007fff05a3b770 error 4 in ld-2.15.so[7f07f6986000+22000]
Feb 25 10:01:15 PCEUBU1 kernel: [ 2584.894387] php5-fpm[10967]: segfault at 7fe42c9cce60 ip 00007fe44fa628e4 sp 00007fff5a86c380 error 4 in ld-2.15.so[7fe44fa53000+22000]

dmesg|grep -i segfault
[ 2584.894387] php5-fpm[10967]: segfault at 7fe42c9cce60 ip 00007fe44fa628e4 sp 00007fff5a86c380 error 4 in ld-2.15.so[7fe44fa53000+22000]

if you need any further information please do not hesitate to ask.

Thanks for your reply. The link to the upstream bug is very helpful, and I appreciate that you had attached the crash report.

> no specific steps or actions from my side at all.

What we're after is an explanation of how to reproduce the bug. If you'd like an update to 12.10, then we need exact steps that others can follow to ensure that the problem is fixed before an update is issued. If I do nothing on a freshly installed 12.10 server, then clearly nothing will crash. So what precisely do I need to do to cause a crash on my screen? Do you see what I mean? The link "How to report bugs effectively" I provided above explains this better.

Please change the bug status back to New once you have posted precise steps on how to reproduce the bug.