Node crashes without any errors - Socket.IO

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Node crashes without any errors
Received-SPF: pass (google.com: domain of webbr...@gmail.com designates 209.85.160.42 as permitted sender) client-ip=209.85.160.42;
MIME-Version: 1.0
Sender: webbr...@gmail.com
In-Reply-To: <CAAO2mOA3KT1W56Rs3=bEEuNDzOXjaWX+EuXT-as2gG9Kgs9...@mail.gmail.com>
References: <CAAO2mOA9XE0UKpg8qJqhcBCExobCKVah7DnxcvinXPaO_nU...@mail.gmail.com>
 <96582AC4-E756-45A7-8698-456B6628C...@kaiser.me> <CAAO2mOCKeyY67+O_P5ZnQR07wok1hq80XoT9nbvAfbHwN4v...@mail.gmail.com>
 <CAAO2mOCMwg5tyDO=zQWHGEXpA2nyumJubdrfK8c68=G0Mcr...@mail.gmail.com>
 <CAAO2mOCFyCRUeRfbuf5_FyedQOrS+6o4qjXA+hwSo4cOuyS...@mail.gmail.com>
 <CAHsm-icDJAV+k2Pgpv0M2KHN3GPq4KGotfB6adNwEQxGgWt...@mail.gmail.com> <CAAO2mOA3KT1W56Rs3=bEEuNDzOXjaWX+EuXT-as2gG9Kgs9...@mail.gmail.com>
From: Brian Gruber <br...@luckyorange.com>
Date: Wed, 25 Apr 2012 17:50:25 -0500
Message-ID: <CAAO2mOAvcDFUapnPUndY+JFbn1z6Wu+u3Uv6VmNVPmuqtL1...@mail.gmail.com>
Subject: Re: Node crashes without any errors
To: socket_io@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Okay, so I've figured out how to ignore that SIGPIPE

handle SIGPIPE nostop

However, I can't get it to break at all when running via gdb. When I
run it outside of gdb it breaks randomly and the only log on my system
is a SEGFAULT. Any idea why running through gdb would NOT generate a
SEGFAULT but running outside of it will?

- Brian

On Tue, Apr 24, 2012 at 4:10 PM, Brian Gruber <br...@luckyorange.com> wrote=
:
> So, if I do
>
> gdb --args node myscript.js
>
> then I type "run"
>
> I quickly get
>
> Program received signal SIGPIPE, Broken pipe.
> 0x00007ffff6616f90 in __write_nocancel () from /lib64/libpthread.so.0
>
> and if I type continue I just keep getting that, so I'm not sure how
> to even let it continue to the point of hitting the segfault.
>
> Sorry, new to gdb and segfault debugging :(
>
>
> On Tue, Apr 24, 2012 at 4:02 PM, Guillermo Rauch <rau...@gmail.com> wrote=
:
>> Try gdb (make sure node is built with debug symbols)
>>
>>
>> On Tue, Apr 24, 2012 at 6:00 PM, Brian Gruber <br...@luckyorange.com> wr=
ote:
>>>
>>> So, it's certainly a segmentation fault, but I can't see any more info
>>> than that in my system logs (dmesg). How would I go about debugging
>>> segmentation faults in node?
>>>
>>> - Brian
>>>
>>> On Tue, Apr 24, 2012 at 2:30 PM, Brian Gruber <br...@luckyorange.com>
>>> wrote:
>>> > Okay, getting closer, I see a SEGFAULT. How do I check the configure
>>> > options used to build node? I remember once playing with SCONS to get
>>> > some memory profiler to work and I can't remember if it's linked to
>>> > the wrong v8? Is that possible?
>>> >
>>> > - Brian
>>> >
>>> > On Tue, Apr 24, 2012 at 1:58 PM, Brian Gruber <br...@luckyorange.com>
>>> > wrote:
>>> >> Started without forever and same thing. Just dies without ANY errors
>>> >> :( =A0In terms of watching memory, I'm monitoring free -m every few
>>> >> seconds and that's where I see the leak if I use node 0.6.*, it
>>> >> steadily rises to 100% used memory. On 0.4.* it doesn't rise and sta=
ys
>>> >> steady, but I have this other issue of just randomly exiting without
>>> >> any messaging.
>>> >>
>>> >> - Brian
>>> >>
>>> >> On Mon, Apr 23, 2012 at 4:42 PM, Nico Kaiser <n...@kaiser.me> wrote:
>>> >>> Brian,
>>> >>>
>>> >>> did you test your server if it leaks memory? ws #43 may be specific=
 to
>>> >>> my application (or large ws servers with many clients), so it would=
 be
>>> >>> interesting if you also see those leaks.
>>> >>>
>>> >>> For the crash... can you start your server without forever? Maybe t=
he
>>> >>> error is displayed then and we can search further.
>>> >>>
>>> >>> Nico
>>> >>>
>>> >>>
>>> >>> On 23.04.2012, at 23:38, Brian Gruber <br...@luckyorange.com> wrote=
:
>>> >>>
>>> >>>> I'm using node 4.12 because all the newer versions seem to have a
>>> >>>> memory leak that makes it unusable as a long running server
>>> >>>> (https://github.com/einaros/ws/issues/43).
>>> >>>> I'm also running socket.io by using the forever module to make sur=
e
>>> >>>> that when things go unexpected it restarts quickly. Problem is, ev=
ery
>>> >>>> few hours "forever" detects that node died but without ANY error
>>> >>>> message. All my logs show that memory is fine, disk is fine, netwo=
rk,
>>> >>>> etc. There's just no error message it dies and forever restarts it=
,
>>> >>>> so
>>> >>>> I have no idea how to debug this.
>>> >>>>
>>> >>>> Any ideas?
>>> >>>>
>>> >>>> - Brian
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Regards,
>>> >>
>>> >> Brian Gruber
>>> >> www.luckyorange.com
>>> >> (913) 735-9032
>>> >>
>>> >> Real time visitor analytics, chat, heatmaps & polls.
>>> >
>>> >
>>> >
>>> > --
>>> > Regards,
>>> >
>>> > Brian Gruber
>>> > www.luckyorange.com
>>> > (913) 735-9032
>>> >
>>> > Real time visitor analytics, chat, heatmaps & polls.
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Brian Gruber
>>> www.luckyorange.com
>>> (913) 735-9032
>>>
>>> Real time visitor analytics, chat, heatmaps & polls.
>>
>>
>>
>>
>> --
>> Guillermo Rauch
>> LearnBoost CTO
>> http://devthought.com
>>
>
>
>
> --
> Regards,
>
> Brian Gruber
> www.luckyorange.com
> (913) 735-9032
>
> Real time visitor analytics, chat, heatmaps & polls.



--=20
Regards,

Brian Gruber
www.luckyorange.com
(913) 735-9032

Real time visitor analytics, chat, heatmaps & polls.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
