The issue is fixed in Emacs 27.x, just checked.

On Tue, Aug 28, 2018 at 11:41 AM উৎসব রায় <uroybd@gmail.com> wrote:

> Here's the backtrace by running 'XFT_DEBUG=16 emacs -Q -xrm
> "emacs.synchronous: true':
>
> fish> bash -c 'XFT_DEBUG=16 emacs -Q -xrm "emacs.synchronous: true"'
> XFT_DEBUG=16
> FontFile /usr/share/fonts/TTF/Hack-Regular.ttf/0 matches new
> Loading file /usr/share/fonts/TTF/Hack-Regular.ttf/0
> FontFile /usr/share/fonts/TTF/Hack-Italic.ttf/0 matches new
> Loading file /usr/share/fonts/TTF/Hack-Italic.ttf/0
> FontFile /usr/share/fonts/TTF/Hack-Regular.ttf/0 matches existing (2)
> FontFile /usr/share/fonts/TTF/Hack-Bold.ttf/0 matches new
> Loading file /usr/share/fonts/TTF/Hack-Bold.ttf/0
> FontFile /usr/share/fonts/TTF/DroidSansDevanagari-Regular.ttf/0 matches new
> Loading file /usr/share/fonts/TTF/DroidSansDevanagari-Regular.ttf/0
> FontFile /usr/share/fonts/TTF/Hack-Regular.ttf/0 matches existing (2)
> FontFile /usr/share/fonts/noto/NotoSansBengaliUI-Regular.ttf/0 matches new
> Loading file /usr/share/fonts/noto/NotoSansBengaliUI-Regular.ttf/0
> Fatal error 11: Segmentation fault
> Backtrace:
> emacs[0x50f73f]
> emacs[0x4f4a72]
> emacs[0x50db6f]
> emacs[0x50dd99]
> emacs[0x50de1a]
> /usr/lib/libpthread.so.0(+0x123c0)[0x7fa340bec3c0]
> emacs[0x5da6cb]
> emacs[0x5de15f]
> emacs[0x57dc08]
> emacs[0x56cced]
> emacs[0x5a8fe1]
> emacs[0x56f654]
> emacs[0x56cc6b]
> emacs[0x56c003]
> emacs[0x42c646]
> emacs[0x438fac]
> emacs[0x5ca81f]
> emacs[0x5ce90b]
> emacs[0x445195]
> emacs[0x443205]
> emacs[0x44b028]
> emacs[0x44fe7b]
> emacs[0x463783]
> emacs[0x46668b]
> emacs[0x56bec7]
> emacs[0x42fe73]
> emacs[0x45369d]
> emacs[0x4fec31]
> emacs[0x502778]
> emacs[0x503e94]
> emacs[0x56be2f]
> emacs[0x4f4e55]
> emacs[0x56bd9e]
> emacs[0x4f4ded]
> emacs[0x4f9fe8]
> emacs[0x4fa328]
> emacs[0x4157eb]
> /usr/lib/libc.so.6(__libc_start_main+0xf3)[0x7fa34052f223]
> emacs[0x41658a]
> fish: “bash -c 'XFT_DEBUG=16 emacs -Q…” terminated by signal SIGSEGV
> (Address boundary error)
>
> On Tue, Aug 28, 2018 at 9:38 AM Noam Postavsky <npostavs@gmail.com> wrote:
>
>> উৎসব রায় <uroybd@gmail.com> writes:
>>
>> > Here's the steps to reproduce.
>> > 1. Open Emacs by running emacs -Q (in GUI).
>> > 2. Open the file mentioned in the original bug report.
>> > 3. That's it, it crashes.
>>
>> I can't reproduce this, but I'm guessing it could be that font thing
>> again.
>>
>> If you run
>>
>>      XFT_DEBUG=16 emacs -Q -xrm "emacs.synchronous: true"
>>
>> does it give some output on the terminal before crashing (as described
>> in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31936#8)?
>>
>> If you can build from git, testing with the latest emacs-26 branch would
>> be helpful too.
>>
> --
> উৎসব রায় (Utsob Roy)
> https://utsob.me
>
-- 
উৎসব রায় (Utsob Roy)
https://utsob.me