Bug 1100958

Summary: [abrt] seamonkey: nsProfileLock::FatalSignalHandler(): seamonkey killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Vadim Raskhozhev <iamdexpl>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: caillon+fedoraproject, dmitry, gecko-bugs-nobody, kengert, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:560c64e64c1563f7857e1cbd7e24a73dab72b688
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-24 12:22:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Vadim Raskhozhev 2014-05-24 13:48:51 UTC 
Description of problem:
Attempt to open http://www.blend4web.com/ru/article/24 crashes SeaMonkey

Version-Release number of selected component:
seamonkey-2.26-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/lib64/seamonkey/seamonkey -no-remote -ProfileManager
crash_function: nsProfileLock::FatalSignalHandler
executable:     /usr/lib64/seamonkey/seamonkey
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 nsProfileLock::FatalSignalHandler at /usr/src/debug/seamonkey-2.26/comm-release/mozilla/profile/dirserviceprovider/src/nsProfileLock.cpp:180
 #3 r300_emit_gpu_flush at r300_emit.c:349
 #4 r300_emit_dirty_state at r300_emit.c:1438
 #5 r300_emit_states at r300_render.c:259
 #6 r300_prepare_for_rendering at r300_render.c:311
 #7 r300_blitter_draw_rectangle at r300_render.c:1143
 #8 util_blitter_clear_custom at util/u_blitter.c:1151
 #9 util_blitter_custom_clear_depth at util/u_blitter.c:1177
 #10 r300_decompress_zmask at r300_blit.c:481
 #11 r300_decompress_zmask_locked_unsafe at r300_blit.c:500
Comment 1 Vadim Raskhozhev 2014-05-24 13:48:54 UTC 
Created attachment 898886 [details]
File: backtrace
Comment 2 Vadim Raskhozhev 2014-05-24 13:48:56 UTC 
Created attachment 898887 [details]
File: cgroup
Comment 3 Vadim Raskhozhev 2014-05-24 13:49:01 UTC 
Created attachment 898888 [details]
File: core_backtrace
Comment 4 Vadim Raskhozhev 2014-05-24 13:49:04 UTC 
Created attachment 898889 [details]
File: dso_list
Comment 5 Vadim Raskhozhev 2014-05-24 13:49:06 UTC 
Created attachment 898890 [details]
File: environ
Comment 6 Vadim Raskhozhev 2014-05-24 13:49:08 UTC 
Created attachment 898891 [details]
File: limits
Comment 7 Vadim Raskhozhev 2014-05-24 13:49:10 UTC 
Created attachment 898892 [details]
File: maps
Comment 8 Vadim Raskhozhev 2014-05-24 13:49:12 UTC 
Created attachment 898893 [details]
File: open_fds
Comment 9 Vadim Raskhozhev 2014-05-24 13:49:15 UTC 
Created attachment 898894 [details]
File: proc_pid_status
Comment 10 Vadim Raskhozhev 2014-05-24 13:49:18 UTC 
Created attachment 898895 [details]
File: var_log_messages
Comment 11 Martin Stransky 2014-06-24 12:22:28 UTC 
This is an automated bug update. We don't use Abrt for tracking Firefox bugs so it may be a crash in other component like plugin-container. If you can reproduce the issue, please remove the [abrt] string from summary and reopen it. Thanks!