pricelessrabbit

> The best thing to do would be to `defer t.Rollback()` right after `db.Begin()`. That way it is impossible for the transaction to leak. `Rollback` is effectively a no-op if...

@konovod right, but i don't understand why. `@y` refers to the current object, but only `@child` is not initialized, so why i can't initialize `@y` after assign `@child`?

oh right :), maybe could i update the doc about this workaround? imho is useful to know because in recursive data structures is quite common to assign self in constructor

i'm currently having the same issue and i can confirm that happens only when i connect multiple monitors and only when i try to use the application with full screen...