Extensions crashes when left running overnight

[ercpe]

Since a few weeks, the plugin crashs when i leave my browser open over night (no hibernate or suspend). Chrome shows the "Extensions has crashed, click to reload" popup.

Is there any way to see what cause this?

(Win 7 64bit, Chrome 43.0.2357.65)

[kepi]

When it crashes, its probably not easy to find any cause. I had those problems about year ago but it is working without any trouble.

My first idea is some memory leak - can you try to check if memory usage rises on your computer after longer period? You should be able to show process list with memory usage with shortcut "shift + escape"

[ercpe]

I left the performance collector running overnight. The memory usage stays constant over the night.

In the apache access log i can see the time when the extension crashed (requests to /icinga/cgi-bin/status.cgi stopping), but i can't correlate this time to any other event on the server :(

[ercpe]

Here is the snippet from chrome's debug log:

[8432:8600:0708/022637:VERBOSE1:resource_loader.cc(434)] OnReadCompleted: "https://myicingahost/icinga/cgi-bin/status.cgi?host=all&limit=0" bytes_read = 32768
[8432:8600:0708/022637:VERBOSE1:resource_loader.cc(434)] OnReadCompleted: "https://myicingahost/icinga/cgi-bin/status.cgi?host=all&limit=0" bytes_read = 13726
[8432:8600:0708/022637:VERBOSE1:web_request_time_tracker.cc(177)] WR percent 31003: https://myicingahost/icinga/cgi-bin/status.cgi?host=all&limit=0: 0/144 = 0.00535926
[8432:8600:0708/022637:VERBOSE1:resource_loader.cc(434)] OnReadCompleted: "https://myicingahost/icinga/cgi-bin/status.cgi?host=all&limit=0" bytes_read = 0
[8432:8600:0708/022637:VERBOSE1:resource_loader.cc(790)] ResponseCompleted: https://myicingahost/icinga/cgi-bin/status.cgi?host=all&limit=0
[8432:4036:0708/022637:INFO:CONSOLE(115)] "traversing data", source: chrome-extension://imaieifkljkcdepgaeommbdgihollphm/inc/background.js (115)

It's seems that the server responds with an empty answer - i suspect a reload/restart of apache due to logrotate or something.
While the server should not respond with an empty answer, the extension should certainly not crash because of this.

[kepi]

Thanks, its definitely helpful and it really can be cause of problem. I'll take a look at it. Cant promise when now unfortunately.

[ercpe]

In the past few days I've tried to debug the crashes to no avail.
I've cluster the code of the extensions with many, many try/catch statements but i was unable to pinpoint the location of the error. At some point, the extension just stops working.

I almost suspect an error in the chrome extension api and/or the use of :(

[kepi]

Thanks for info. I'm currently trying to implement some long postponed changed and I'll be rewriting some core parts. I hope that in the process this problem will be fixed too. It should be ready in few weeks I hope.

[Elikster]

Since the new update of Chrome, I have been noticing this behavior happening again, with same set of problems as posted by other user, with leaving the chrome running overnight, and then disappear in the morning.

It was not an issue in the past, but now it it is.

[kepi]

This extension is currently abandoned. I'm not planning to fix this issues any time soon unfortunately, sorry for that. I may decide to give it a go in future.