1051216 - Nightly crashes while responding to PM in SUMO

Status: RESOLVED FIXED

(Core :: Widget: Win32, defect)

Description

[CAK]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0 (Beta/Release)
Build ID: 20140808030201

Steps to reproduce:

Twice while responding to SUMO forum PMs, Nightly crashed
Crash is not reproducible. It happened at random times.
A few days ago I installed Lazarus: Form Recovery 2.3

Here are the crash reports:
https://crash-stats.mozilla.com/report/index/bp-de5f47e6-a728-4f83-b2b3-644d32140809

https://crash-stats.mozilla.com/report/index/bp-c49403cc-fc2c-4123-87c2-827442140809

Comment 1

[Loic]

Many add-ons in your Nightly profile, maybe one of them is the culprit.

Comment 2

[CAK]

(In reply to Loic from comment #1)
> Many add-ons in your Nightly profile, maybe one of them is the culprit.

Hi! Thanks for the review! :)

Possibly it's one of the add-ons although I suspect either the latest build or Lazarus (add-on) or a combination of the two since the problem started in the last couple of days. (All my other add-ons are older and didn't cause me any trouble so far).

In any case I didn't expect a solution (as I said, it's not reproducible). It is just for reference in case others start having the same problem (especially with SUMO forum posts/PMs)

Thanks again for your review. :)

Comment 3

[Loic]

Maybe you can try to answer a PM and play with Lazarus (like restarting Nightly after typing text). AFAIK Lazarus saves forms and their content.

Comment 4

[CAK]

I'm replying to PMs all the time but I don't get the crash every time. :)

Yes, Lazarus saves forms and their content (if you don't have it, you should try it!). There is a chance that when Lazarus tries to save the content (auto-save) there is a problem and Fx crashes. I'll keep testing it and see how it goes.

Thanks for your review and help again! :)

Comment 5

[:Gijs (he/him)]

The crash is in IME Windows code called from Firefox... not sure what would cause that; perhaps the thing that the windows code is trying to notify about the end of the edit has gone away? If this is due to a race condition, that would explain why it doesn't reproduce reliably... CAK, do you use IME input? Any news regarding Lazarus influencing this? :-)

Comment 6

[CAK]

(In reply to :Gijs Kruitbosch from comment #5)
> The crash is in IME Windows code called from Firefox... not sure what would
> cause that; perhaps the thing that the windows code is trying to notify
> about the end of the edit has gone away? If this is due to a race condition,
> that would explain why it doesn't reproduce reliably... CAK, do you use IME
> input? Any news regarding Lazarus influencing this? :-)

Hi! :)

No, I don't use IME input. Unfortunately I haven't been able to determine a pattern to the crash other than:

It MAY BE affected by the tab remaining open for some time without editing being done. What I mean is:
1. I read a PM and then click on reply.
2. Start typing my reply and then change to another tab to collect some information
3. Return to the PM tab and continue to type
4. Fx crashes.

The problem is that this does not happen every time so my observations may be total nonsense. I've tried many times to reproduce it (trying to duplicate exactly what I did before) with no luck. I don't know if additional crash reports would help pinpointing the problem. Let me know. :) 

Regarding Lazarus: 
It's a toughie. Removing it and going for some time without Fx crashing does not necessarily mean that Lazarus is the culprit simply because it doesn't happen all the time. (And Lazarus has suddenly become a necessity BECAUSE of those crashes! ;) (It has really saved me from a lot of trouble having to re-type the entire PM)

Plus: My Nightly is really being "tortured" because of my involvement with AoA. Too many tabs open and close at a fast pace which may cause Fx to leak or get out of control. :)

Let me know if you need any more info. I'm here to help. :)

Comment 7

[Liz Henry (:lizzard)]

The crash signature associated with this is showing up as a topcrasher on Nightly in bug 1053885.

Comment 8

[Liz Henry (:lizzard)]

There's only one crash now with this in the last week; this seems to have been fixed in bug 1053885. I think we can safely close the bug.