Atom Shell application random crashing- best debug method?


#1

We’ve been developing an atom-shell application for a web-based video suite for some time now, but after our last code sprint we noticed that our application would crash after 1-5 minutes. We’re really not sure how to begin to find the problem as it sort of appeared randomly.

Here’s a typical output during a crash…

[7460:0129/115251:ERROR:browser_main_loop.cc(163)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[7488:0129/115251:INFO:renderer_main.cc(207)] Renderer process started
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[7460:0129/115300:INFO:CONSOLE(37)] "Loading project", source: file:///home/seve/workspace/atom-shell/video-feed-desktop/js/loader/loader.js (37)
[7525:0129/115300:INFO:renderer_main.cc(207)] Renderer process started
[7527:0129/115300:INFO:renderer_main.cc(207)] Renderer process started
[7460:0129/115300:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue
Crash dump id: d6bccf40-db16-4f91-be56-46088794f549
Aborted (core dumped)

(the crash dump id is consistent across crashes)
We really don’t want to have to port the application but we’re on a tight deadline, any help appreciated!


#2

Problem resolved!

It turns out this had to do with maintaining the global window reference. The window was doing things but it’s reference was gone- as a result the garbage collector removed it at a seemingly random time.