On Sun, 2013-02-24 at 13:01 +1300, Aidan Gill wrote:
> What more information can I provide to help debug this?
>
I tried too, and can't reproduce the issue, though it can be because I'm
testing on Linux.
Can you give us more details on what you did, especially the "copy
something from a text field", because if you copy something in the grid,
there's no data changed in the grid, so I don't see why you have such a
message. Here is what I did:
* add a database with this contents CREATE TABLE t1(c1 serial PRIMARY KEY, c2 text); INSERT INTO t1 (c2) SELECT 'Line
'||iFROM generate_series(1, 10000) AS i;
* on the pgAdmin browser window * connect to the new database * right click on the table t1 * choose "View Top 100
Rows"in the contextual menu
* on the EditGrid window opened after my last action * click on line 10, column c2 * changed the text, and hit Enter *
*cannotclick on Save as it is done when I hitted the Enter key* * click the Resfresh icon in the toolbar
It did the refesh, but no crash, no message.
> On 24 February 2013 12:58, Michael Shapiro <mshapiro51@gmail.com> wrote:
>
> > I am running Window 7 (64bit), PgAdmin 1.16.1
> > I can not replicate this problem. It does not cause a crash.
> >
> >
> >
> > On Sat, Feb 23, 2013 at 5:31 PM, Aidan Gill <aidang@gmail.com> wrote:
> >
> >> I can reliably reproduce this crash, both with pgAdmin 1.14 and pgAdmin
> >> 1.16.1.
> >>
> >> I'm running the latest Windows version. To reproduce the crash I view the
> >> top 100 rows of data in a table (one or more records, it doesn't matter),
> >> copy something from a text field, wait for the database to change that text
> >> field, then click the Refresh icon, and 'No' to 'There is unsaved data in a
> >> row'. pgAdmin freezes then crashes reliably every single time in both
> >> versions.
> >>
> >> I've set up logging to debug but it doesn't provide any useful
> >> information beyond that.
> >>
> >
> >
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
