Re: Mac SM 2.0.1 Crash - on random Master Password request.
On Thu, 31 Dec 2009 11:29:10 -0800, Rufus wrote: Other odd thing was that the SM Crash Reporter came up in a different Space than SM was opened into - SM assigned to Space 2; SM Crash Reporter came up in Space 1. I entered a description in the Crash reporter and relaunched SM and it launched/ran normally. You didn't tell us the crash ID so we can't help you there. Go to about:crashes . Your crash should be the most recent listed. Copy and paste the URL here in this thread. The Crash Reporter is a separate process (and process name). You could try pinning the crash reporter to the same workspace as SeaMonkey itself. Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Mac SM 2.0.1 Crash - on random Master Password request.
Philip Chee wrote: On Thu, 31 Dec 2009 11:29:10 -0800, Rufus wrote: Other odd thing was that the SM Crash Reporter came up in a different Space than SM was opened into - SM assigned to Space 2; SM Crash Reporter came up in Space 1. I entered a description in the Crash reporter and relaunched SM and it launched/ran normally. You didn't tell us the crash ID so we can't help you there. Go to about:crashes . Your crash should be the most recent listed. Copy and paste the URL here in this thread. The Crash Reporter is a separate process (and process name). You could try pinning the crash reporter to the same workspace as SeaMonkey itself. Phil Ok - that makes sense...new to this... http://crash-stats.mozilla.com/report/index/bp-fb88e14c-5fe7-49a6-957a-7da662091230 Looks like I've actually had two crashes since install - here's the other one: http://crash-stats.mozilla.com/report/index/bp-81c77584-38b1-4480-9beb-3afa72091221 Something else strange is that even though I've fixed the window not in front at launch problem I was having, SM 2.x.x does the hokey-pokey with Spaces when I launch it - i.e.; when I launch SM (assigned to Space 2) the app returns to Space 1, displays the SM Menu bar, then moves to Space 2 and opens the window. Because I had solved the previous issue by rebuilding Launch Services, I had assumed this was an OS X issue and not a SM issue - now I'm not so sure...SM 1.1.18 doesn't do this. -- - Rufus ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Mac SM 2.0.1 Crash - on random Master Password request.
Had my first SM 2.x.x crash last night - in fact, it was my first genuine SM crash ever. Was using SM 2.0.1 on my MacBook Pro running SnoLep. I was on my Home Page selecting a Bookmark - at this point, the Master Password was requested, and SM appeared to freeze; I could not actually enter the Master Password, nor could I get the Bookmarks panes to close by clicking off them. After some clicking around I was able to get the Bookmarks panes to close one by one - but when I got the screen cleared SM crashed when I clicked into the Master Password pane. Other odd thing was that the SM Crash Reporter came up in a different Space than SM was opened into - SM assigned to Space 2; SM Crash Reporter came up in Space 1. I entered a description in the Crash reporter and relaunched SM and it launched/ran normally. I have also seen this behavior using SM 1.1.18, but never a crash - just that SM freezes and I have had to Force Quit SM and relaunch to recover. This freeze always happens during a request for Master Password which seemingly occurs at random - i.e.; I have my pref set to request the Master the first time it is needed and I have not navigated to or selected anything where a password is required and the request for Master comes up anyway. Under 1.1.18 this often occurs during a download, but it can also happen at other times. Under 2.0.1 this had generally been recoverable without Force Quit, but still happens. This time it actually crashed. -- - Rufus ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
