Closed
Bug 1248324
Opened 8 years ago
Closed 8 years ago
CRASH after double-click on Title Bar
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
seamonkey2.44
People
(Reporter: benl234, Unassigned)
References
Details
(Keywords: crash, regression, Whiteboard: [DUPEME? BUG 1246404])
Attachments
(1 file)
4.02 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 SeaMonkey/2.44a1 Build ID: 20160205232941 Steps to reproduce: Double-clicked the title bar. Actual results: Seamonkey window disappeared and shortly afterwards the crash reporter window appeared. Expected results: Seamonkey should have maximized or un-maximized its window.
I wasn't sure if I was supposed to submit a bug after sending the crash reports also. crash ids: bp-7334edd2-ab40-40bb-84d4-95e512160207 bp-b42e6c03-96b0-43ef-8384-e79462160207 bp-4ada683e-91f4-4269-8891-c9b552160207 Hunting around in crash-stats.mozilla.com it says there's another bug with the same "signature," from someone else: bp-058a271d-e1ea-472a-b6b2-33ad42160209 Thank you, -Ben
Component: OS Integration → General
Comment 2•8 years ago
|
||
REPRODUCIBLE with unofficial (from <http://seamonkey.callek.net/contrib/>) en-US SeaMonkey 2.44a1 Mozilla/5.0 (Windows NT 6.1; x64; rv:47.0) Gecko/20100101 Firefox/47.0 Build 20160208090255 (Default Classic Theme) on German WIN7 64bit: 1. Launch SeaMonkey » Browser appears 2. Double click Title Bar (for explicaton see <http://www.computerhope.com/jargon/t/titlebar.htm>) CRASH
Comment 3•8 years ago
|
||
a) Was still ok with unofficial (from <http://seamonkey.callek.net/contrib/>) English SeaMonkey 2.43a1 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 Build 20160116041507 (Default Classic Theme) on German WIN7 64bit, where double clicks window full size / window partial size
Comment 4•8 years ago
|
||
b) Also crashes in safe mode, with new user profile c) Also crashes Mail, Chatzilla, Reminderfox d) No crash with TB 47.0a1 (2016-02-08) e) No crash with FF 47.0a1 (2016-02-12)
Severity: normal → critical
Keywords: crash
Summary: double-clicking the title bar crashes seamonkey every time. → CRASH after double-click on Title Bar
Comment 5•8 years ago
|
||
f) Crashes also with Modern Theme g) Crashes with double click on any OS Windows border (left, right, bottom), not only title bar.
Comment 6•8 years ago
|
||
h) NOT reproducible REPRODUCIBLE with English SeaMonkey 2.44a1 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build 20160208023510 (Default Classic Theme) on VirtualBox Ubuntu 14.04 LTS
Comment 7•8 years ago
|
||
Not reproducable with private x64 VS2015 en-US build from today in Virtualbox VM and fresh profile on real hardware with AMD R9 280X (this one did crash during profile creation once). User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0 SeaMonkey/2.44a1 Build identifier: 20160215081940 There were some nasty bugs in the tree until a few days ago. I suggest to check it again when a new build becomes available. If it still crashes please state which also video adapter. Rainers is with Nvidia.
Comment 9•8 years ago
|
||
This was likely caused by Bug 1246404
Updated•8 years ago
|
Whiteboard: [DUPEME? BUG 1246404]
Reporter | ||
Comment 10•8 years ago
|
||
User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0 SeaMonkey/2.44a2 Well, anyway, for me the bug no longer happens in Seamonkey 2.44a2. Double-clicking the title bar works as expected, toggles state of window maximization.
Comment 11•8 years ago
|
||
(In reply to benl from comment #10) > User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 > Firefox/47.0 SeaMonkey/2.44a2 > > Well, anyway, for me the bug no longer happens in Seamonkey 2.44a2. > > Double-clicking the title bar works as expected, toggles state of window > maximization. Thanks for letting us know.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•