Bug 969546 - [abrt] pgadmin3-1.16.1-1.fc19: g_malloc: Process /usr/bin/pgadmin3 was killed by signal 11 (SIGSEGV)
Summary: [abrt] pgadmin3-1.16.1-1.fc19: g_malloc: Process /usr/bin/pgadmin3 was killed...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pgadmin3
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Devrim Gündüz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9e96c2802441c55b3c309ced63a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-31 18:43 UTC by M. Edward (Ed) Borasky
Modified: 2015-02-17 15:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:24:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (89.68 KB, text/plain)
2013-05-31 18:43 UTC, M. Edward (Ed) Borasky
no flags Details
File: cgroup (140 bytes, text/plain)
2013-05-31 18:43 UTC, M. Edward (Ed) Borasky
no flags Details
File: core_backtrace (2.98 KB, text/plain)
2013-05-31 18:43 UTC, M. Edward (Ed) Borasky
no flags Details
File: dso_list (10.42 KB, text/plain)
2013-05-31 18:43 UTC, M. Edward (Ed) Borasky
no flags Details
File: environ (2.35 KB, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details
File: limits (1.29 KB, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details
File: maps (53.21 KB, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details
File: open_fds (265 bytes, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details
File: proc_pid_status (914 bytes, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details
File: var_log_messages (325 bytes, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details
File: xsession_errors (3.12 KB, text/plain)
2013-05-31 18:44 UTC, M. Edward (Ed) Borasky
no flags Details

Description M. Edward (Ed) Borasky 2013-05-31 18:43:44 UTC
Description of problem:
1. Logged into the 'postgres' Linux user
2. Started PgAdmin3
3. Opened the PostgreSQL 'postgres' user
4. Defined a password.
5. Closed the password dialog and PgAdmin3 crashed.

Version-Release number of selected component:
pgadmin3-1.16.1-1.fc19

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        pgadmin3
crash_function: g_malloc
executable:     /usr/bin/pgadmin3
kernel:         3.9.4-300.fc19.x86_64
runlevel:       N 5
uid:            26

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_malloc at gmem.c:159
 #3 g_malloc_n at gmem.c:400
 #4 miRegionOp at gdkregion-generic.c:873
 #5 gdk_region_intersect at gdkregion-generic.c:609
 #6 gdk_window_invalidate_maybe_recurse_full at gdkwindow.c:5919
 #11 _gdk_window_process_expose at gdkgeometry-x11.c:317
 #12 gdk_event_translate at gdkevents-x11.c:1645
 #13 _gdk_events_queue at gdkevents-x11.c:2336
 #19 gtk_main at gtkmain.c:1257
 #20 wxEventLoop::Run at src/gtk/evtloop.cpp:76

Comment 1 M. Edward (Ed) Borasky 2013-05-31 18:43:49 UTC
Created attachment 755336 [details]
File: backtrace

Comment 2 M. Edward (Ed) Borasky 2013-05-31 18:43:53 UTC
Created attachment 755337 [details]
File: cgroup

Comment 3 M. Edward (Ed) Borasky 2013-05-31 18:43:57 UTC
Created attachment 755338 [details]
File: core_backtrace

Comment 4 M. Edward (Ed) Borasky 2013-05-31 18:43:59 UTC
Created attachment 755339 [details]
File: dso_list

Comment 5 M. Edward (Ed) Borasky 2013-05-31 18:44:02 UTC
Created attachment 755340 [details]
File: environ

Comment 6 M. Edward (Ed) Borasky 2013-05-31 18:44:07 UTC
Created attachment 755341 [details]
File: limits

Comment 7 M. Edward (Ed) Borasky 2013-05-31 18:44:10 UTC
Created attachment 755342 [details]
File: maps

Comment 8 M. Edward (Ed) Borasky 2013-05-31 18:44:13 UTC
Created attachment 755343 [details]
File: open_fds

Comment 9 M. Edward (Ed) Borasky 2013-05-31 18:44:15 UTC
Created attachment 755344 [details]
File: proc_pid_status

Comment 10 M. Edward (Ed) Borasky 2013-05-31 18:44:18 UTC
Created attachment 755345 [details]
File: var_log_messages

Comment 11 M. Edward (Ed) Borasky 2013-05-31 18:44:21 UTC
Created attachment 755346 [details]
File: xsession_errors

Comment 12 Fedora End Of Life 2015-01-09 18:16:59 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 M. Edward (Ed) Borasky 2015-01-09 18:46:14 UTC
Surely this has been fixed by now - I've used pgadmin3 many times in the life of F20 and now F21 with no crashes.

Comment 14 Fedora End Of Life 2015-02-17 15:24:37 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.