On 29/06/2017 02:15, bo1953 wrote: > My apologies for 'hijacking' a previous thread about the above question, > no offense meant in the least bit. > > Below, as requested, I have pasted the 'Submitted Crash Reports' or do I > need to post the individual content of each report or several or ??? > > My crash reports go back to Nov 2016. > > TIA for your input and thoughts on what my system requires. > > Report ID Date Submitted > bp-21aa3c38-053b-401e-ae16-4d81e0170625
out of memory > bp-bff9f312-b127-4074-9c2f-bda440170622 out of memory > bp-a1655016-2c12-4262-9b29-558b30170622 https://crash-stats.mozilla.com/report/index/a1655016-2c12-4262-9b29-558b30170622 [@ nvwgf2um.dll | BaseThreadInitThunk ] https://bugzilla.mozilla.org/show_bug.cgi?id=1310600 https://bugzilla.mozilla.org/show_bug.cgi?id=1292273 Are your Nvidia graphics drivers up-to-date? > bp-a44c8a81-876a-4fde-a0b8-bd4780170615 https://crash-stats.mozilla.com/report/index/a44c8a81-876a-4fde-a0b8-bd4780170615 [@ nsIContent::HasAttr ] Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x18 > bp-9afb45d9-cf6d-4e55-9b05-5783c0170615 out of memory > bp-2b92df6d-7376-4244-9ed2-343130170603 out of memory Hmmm, I wonder if the EXCEPTION_ACCESS_VIOLATION_READ errors are in fact an OOM that wasn't diagnosed, and then we just try to dereference a NULL struct which gives a small offset... But I thought that's not possible in C++, that memory allocation failures raised an exception... FRG, is it possible that some allocs use malloc? Or actually catch the OOM exception and keep going? I agree that increasing the amount of RAM might make a difference. Worth a try. Otherwise, Mozilla is known to leak memory. So taking the habit of closing the session every few hours might also avoid the OOM situations. Regards. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
