Re: Crash Report

JAS wrote: WaltS48 wrote: JAS wrote: Frank-Rainer Grahl wrote: Have not seen this one before. I would update to 2.49.4 first. 2.48 is ancient. Backup you profile before. FRG JAS wrote: I am using SM 2.48 on Windows 7, lately when I click an item to "save as" in Foxit PDF or just a downloa

Re: Crash Report

WaltS48 wrote: JAS wrote: Frank-Rainer Grahl wrote: Have not seen this one before. I would update to 2.49.4 first. 2.48 is ancient. Backup you profile before. FRG JAS wrote: I am using SM 2.48 on Windows 7, lately when I click an item to "save as" in Foxit PDF or just a download or photo m

Re: Crash Report

JAS wrote: Frank-Rainer Grahl wrote: Have not seen this one before. I would update to 2.49.4 first. 2.48 is ancient. Backup you profile before. FRG JAS wrote: I am using SM 2.48 on Windows 7, lately when I click an item to "save as" in Foxit PDF or just a download or photo my Seamonkey quit

Re: Crash Report

Just drop it over the main Windwow and it should install. If not you probably have some profile corruption or something else on you PC is going on. Try safe mode and then a new test profile first. FRG JAS wrote: Frank-Rainer Grahl wrote: Have not seen this one before. I would update to 2.49.

Re: Crash Report

Frank-Rainer Grahl wrote: Have not seen this one before. I would update to 2.49.4 first. 2.48 is ancient. Backup you profile before. FRG JAS wrote: I am using SM 2.48 on Windows 7, lately when I click an item to "save as" in Foxit PDF or just a download or photo my Seamonkey quits respondin

Re: Crash Report

Have not seen this one before. I would update to 2.49.4 first. 2.48 is ancient. Backup you profile before. FRG JAS wrote: I am using SM 2.48 on Windows 7, lately when I click an item to "save as" in Foxit PDF or just a download or photo my Seamonkey quits responding and I finally have to cli

Crash Report

I am using SM 2.48 on Windows 7, lately when I click an item to "save as" in Foxit PDF or just a download or photo my Seamonkey quits responding and I finally have to click the option to shutdown. I listed the last two crashes: http://crash-stats.mozilla.com/report/index/bp-7ef883f8-b045-4ee8-8

Re: New Crash Report Situation (W10 pro, 32b, desktop)

Adrian Kalla wrote: W dniu 02.07.2017 o 18:43, bo1953 pisze: Frank-Rainer Grahl wrote: The last two are out of memory errors. Do you have only 2GB in your PC? If yes upgrade to 4 GB and see if the errors go away. 2GB and any recent Windows version asks for trouble. You forgot about this: Bu

Re: New Crash Report Situation (W10 pro, 64b, desktop)

On 02/07/2017 20:15, Bo1953 wrote: > Adrian Kalla wrote: >> W dniu 02.07.2017 o 18:43, bo1953 pisze: >>> Frank-Rainer Grahl wrote: The last two are out of memory errors. Do you have only 2GB in your PC? If yes upgrade to 4 GB and see if the errors go away. 2GB and any recent Windows

Re: New Crash Report Situation (W10 pro, 64b, desktop)

Adrian Kalla wrote: W dniu 02.07.2017 o 18:43, bo1953 pisze: Frank-Rainer Grahl wrote: The last two are out of memory errors. Do you have only 2GB in your PC? If yes upgrade to 4 GB and see if the errors go away. 2GB and any recent Windows version asks for trouble. You forgot about this: Bu

Re: New Crash Report Situation (W10 pro, 64b, desktop)

W dniu 02.07.2017 o 18:43, bo1953 pisze: > Frank-Rainer Grahl wrote: >> The last two are out of memory errors. Do you have only 2GB in your PC? >> If yes upgrade to 4 GB and see if the errors go away. 2GB and any >> recent Windows version asks for trouble. You forgot about this: > Build Architec

Re: New Crash Report Situation (W10 pro, 64b, desktop)

8b373-e292-4a8b-9cec-a95790170509 09-May-1715:42 bp-de34c437-bf1b-4c7a-ae5a-a15b80170509 08-May-1721:30 05c496c5-9786-4003-9c82-cc815bfa1043 23-Apr-1717:06 The most recent content: SeaMonkey 2.46 Crash Report [@ OOM | small ] Search Mozilla Support for this signature How to re

Re: New Crash Report Situation (W10 pro, 64b, desktop)

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 ??? >

Re: New Crash Report Situation (W10 pro, 64b, desktop)

70509 09-May-1715:42 bp-de34c437-bf1b-4c7a-ae5a-a15b80170509 08-May-1721:30 05c496c5-9786-4003-9c82-cc815bfa1043 23-Apr-1717:06 The most recent content: SeaMonkey 2.46 Crash Report [@ OOM | small ] Search Mozilla Support for this signature How to read this crash report ID

New Crash Report Situation (W10 pro, 64b, desktop)

:42 bp-de34c437-bf1b-4c7a-ae5a-a15b80170509 08-May-17 21:30 05c496c5-9786-4003-9c82-cc815bfa1043 23-Apr-17 17:06 The most recent content: SeaMonkey 2.46 Crash Report [@ OOM | small ] Search Mozilla Support for this signature How to read this crash report ID: 21a

Re: about:crashes command shows one crash report that won't go away forever.

sh Reports'? :) > > Yes. > > >>> What the frak? How do I remove this stuck one? Where is it stored? >> >> You are using Win, so you have to adapt the above path. Then look there >> in the subdirectory submitted. > > Woohoo! C:\Documents and

about:crashes command shows one crash report that won't go away forever.

Hello again. I noticed my Windows XP Pro. SP3's SeaMonkey v2.17.1's about crashes web page keeps showing a submitted crash report dump from 2/17/2013 10:04 PM PT. I remove all reports and nothing is shown. If I refresh/reload this about:crashes web page, then it comes back. Wha

Re: about:crashes command shows one crash report that won't go away forever.

ere in the subdirectory submitted. Woohoo! C:\Documents and Settings\Username\Application Data\Mozilla\SeaMonkey\Crash Reports\pending\ ... I saw the two old crash report files. I manually deleted without restarting SM and they were gone forever! Yeah, good job and thanks. :) -- "Ants never l

Re: about:crashes command shows one crash report that won't go away forever.

, so you have to adapt the above path. Then look there >>> in the subdirectory submitted. >> >> Woohoo! C:\Documents and Settings\Username\Application >> Data\Mozilla\SeaMonkey\Crash Reports\pending\ ... I saw the two old >> crash report files. I manually

Re: about:crashes command shows one crash report that won't go away forever.

Ant: >I noticed my Windows XP Pro. SP3's SeaMonkey v2.17.1's about crashes web >page keeps showing a submitted crash report dump from 2/17/2013 10:04 PM >PT. I remove all reports and nothing is shown. If I refresh/reload this >about:crashes web page, then it comes ba

Re: Crash Report [@ LdrShutdownProcess ] with Flash 11.3

On 12-07-21 2:57 AM, Ray_Net wrote: I experiences the bug https://bugzilla.mozilla.org/show_bug.cgi?id=747683 Could somone tell me in what SM version it's corrected ? I currently have Build identifier: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8 If I'm read

Crash Report [@ LdrShutdownProcess ] with Flash 11.3

I experiences the bug https://bugzilla.mozilla.org/show_bug.cgi?id=747683 Could somone tell me in what SM version it's corrected ? I currently have Build identifier: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8 ___

These files are the crash report.

These two files are created when Seamonkey has crashed and a crash report has been sent to Mozilla developers. I opened the file with the extension .extra and this is what I could read: Theme=classic/1.0 StartupTime=1301702970 ServerURL=https://crash-reports.mozilla.com/submit Add-ons=en

Re: Seamonkey 2.0.14 crash report

Paul B. Gallagher wrote: user@domain.invalid wrote: I was debugging a PAM issue and a Google search "debugging PAM modules" returned a Red Hat link that looked very interesting but clicking on it causes SeaMonkey 2.0.14 under Windows XP to blow away:

Re: Seamonkey 2.0.14 crash report

user@domain.invalid wrote: I was debugging a PAM issue and a Google search "debugging PAM modules" returned a Red Hat link that looked very interesting but clicking on it causes SeaMonkey 2.0.14 under Windows XP to blow away:

Re: Seamonkey 2.0.14 crash report

Jay Garcia wrote: On 18.05.2011 10:39, user@domain.invalid wrote: --- Original Message --- I was debugging a PAM issue and a Google search "debugging PAM modules" returned a Red Hat link that looked very interesting but clicking on it causes SeaMonkey 2.0.14 under Windows XP to blow away: h

Re: Seamonkey 2.0.14 crash report

On 18.05.2011 10:39, user@domain.invalid wrote: --- Original Message --- > I was debugging a PAM issue and a Google search "debugging PAM modules" > returned a Red Hat link that looked very interesting but clicking on it > causes SeaMonkey 2.0.14 under Windows XP to blow away: > > https://osu.r

Seamonkey 2.0.14 crash report

I was debugging a PAM issue and a Google search "debugging PAM modules" returned a Red Hat link that looked very interesting but clicking on it causes SeaMonkey 2.0.14 under Windows XP to blow away: https://osu.redhat.com/content/courses/rha250-50-trial1/tag_userauth/tag_lessons/tag_pam/tag_discu