Hi\!

I cannot reproduce this. Could you give some more detail:
a\) There are a whole bunch of copy-actions: Copy selection literally, Copy commands only, and Copy lines to output. Which were you using? From the Edit->Menu? From the RMB context menu? Using a keyboard shortcut?
b\) Perhaps the content of the R console is relevant? Could you give an example that triggers the crash? Are you trying to copy everything, or only a specific range?

Regards
Thomas

- **summary**: Crash when copying from R terminal --> NEEDINFO: Crash when copying from R terminal

-- Originally posted by (AT sourceforge.net): nalimilan --
I've found one important factor: it only happens when using focus follows mouse. I understood that by reading the part of the Qt code that crashes \(see below\).

About your questions: it happens when merely trying to copy a few chars using the Copy item from the top of the context menu of the terminal, or the Edit->Copy item. Copy to Output works, though. So the content of the terminal doesn't seem relevant.

I'm getting a Broken Install error dialog on start, but RKward works very well despite it, so I'm not sure it can be related \(how can I find out what exactly is broken in my installation?\).

2800	    //Whenever we leave an alien widget on X11, we need to reset its nativeParentWidget\(\)'s cursor.
2801	    // This is not required on Windows as the cursor is reset on every single mouse move.
2802	    QWidget \*parentOfLeavingCursor = 0;
2803	    for \(int i = 0; i < leaveList.size\(\); ++i\) \{
2804	        w = leaveList.at\(i\);
2805	        if \(\!isAlien\(w\)\)
2806	            break;
2807	        if \(w->testAttribute\(Qt::WA\_SetCursor\)\) \{
2808	            QWidget \*parent = w->parentWidget\(\);
2809	            while \(parent && parent->d\_func\(\)->data.in\_destructor\)

Thanks for the additional info. I still cannot reproduce the problem, even when using Focus follows mouse.

The backtrace does not contain anything RKWard-related \(or even just KDE-related\), so it is quite likely that the bug is on a lower level. For starters, could you try, whether you can trigger similar crashes in the script editor \(try using "Copy" from the context menu\) or even in a standalone kwrite?

Since you seem to have some debugging skills, perhaps you could try running rkward through valgrind:
rkward --debugger valgrind
Quite likely, the root cause of the crash is simply not visible in the backtrace, but rather something went wrong shortly before, and then the next iteration of event processing crahes. Perhaps valgrind will give some better hints.

Regarding the message about a broken installation, this is \_probably\_ unrelated, but it's certainly a good idea to fix this, and thus rule out that this has anything to do with the problem. See the "troubleshooting" section on http://p.sf.net/rkward/faq .

Regards
Thomas

-- Originally posted by (AT sourceforge.net): nalimilan --
Valgrind log shown after I click on Copy
-- Created an attachment --

-- Originally posted by (AT sourceforge.net): nalimilan --
Copying in the script editor works OK, so that's not Kate's fault. Note it works well with RKward packaged in Fedora 15, and I built the SVN version with the same Qt, so that probably comes from a change in RKward.

I just discovered it also happens when clicking other menu items that don't bring up a dialog \(e.g. Erase\). You also need to have a script file open for the crash to happen. So that must come from a focus change issue: when you click on the Copy menu item, the menu closes and the mouse is over the script file, which gets focused. Maybe at that point RKward tries to unfocus the menu, which has already been destroyed?

See the attached Valgrind log, which shown many things happen just when I click on the Copy menu item. An interesting track is the delete called from RKWardMainWindow::partChanged\(\).

Thanks for those additional hints. With this, I finally managed to reproduce the crash. For this, I had to create a situation, where the context menu would overlap with a second, inactive, window \(e.g. a script window\). Then, either
a\) moving the mouse into the second window, while the context menu is still shown, or
b\) selecting an action from the context menu which is positioned over the second window
would result in the crash. Problem was that this would activate the second window, which in turn would lead to the destruction of the context menu, while the context menu is still running its event loop.

I've fixed this in SVN. Please test, whether this also fixes the issue for you.

Regards
Thomas

- **summary**: NEEDINFO: Crash when copying from R terminal --> NEEDS TESTING: Crash when copying from R terminal

-- Originally posted by (AT sourceforge.net): nalimilan --
Great, it's fixed\! Very efficient\!

-- Originally posted by (AT sourceforge.net): nalimilan --
- **summary**: NEEDS TESTING: Crash when copying from R terminal --> FIXED IN SVN: Crash when copying from R terminal
- **status**: open --> open-fixed

- **status**: open-fixed --> closed-fixed