Open the attached document in Writer
Find the hypertext link "http://theWebalyst.com/newsletter"
Right click on the link and choose Edit
Edit the target link (e.g. backspace to delete the 'r' in newsletter, then press 'r' to restore it)
Note: this is not specific to this hyperlink or this document. Embedded hyperlinks are fraught with problems, this is just one of the most severe and easily reproduced I've encountered. I don't understand why you marked my report 33596 instead of using it to do a more thorough testing of this area. I didn't split out the bugs because they were so numerous that I don't have time to do it, and thought it best for someone to look at the code and then test it properly. Clearly this code has some major problems!
OS: Windows 7 SP1 64bit (dual monitor active)
Could you provide the sample document please?
Created attachment 49075 [details]
Writer doc containing hyperlink, which when edited causes crash
I think one way to trigger a crash is to edit an existing link, place the cursor at the end of the "Target" URL and type a character.
E.g. in the attached doc:
Right click on the link "http://theWebalyst.com/newsletter"
Place cursor at end of "http://theWebalyst.com/newsletter#id=wm1f_w"
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
In 3.5.0 still reproducible?
I'm not touching 3.5 until it is hardened -> I tried RC3 and within seconds of editing a spreadsheet in it Calc 3.5 crashed, so I have reverted to 3.4.
My comment is that LibreOffice needs a more robust regression testing process. Automation is probably needed, but it takes a lot of effort to set up.
> I tried RC3 and within seconds of editing a spreadsheet in it Calc 3.5 crashed
It is very interesting. This crash was reproducible by doing the same thing again or it was crashed in random moments?
And in 3.4 Writer crash with attached file reproducible?
I'm sorry but I don't have much more information. I had work to do and so uninstalled 3.5 immediately. Here is what I know...
What I was doing was inserting a few rows using Ctrl-+ (having selected a row), and some copy and pasting into the new rows.
The crash happened within seconds of opening an existing (simple) v3.4 spreadsheet and starting to work on it in 3.5. So I went on to do similar operations in 3.4 without problems (although I can't be 100% certain I used the same keystrokes).
Thanks for information. I will try to reproduce problem.
I just installed 3.5 release and went to edit a hyperlink in my ebook template and it crashes reliably.
(In reply to comment #10)
> I just installed 3.5 release and went to edit a hyperlink in my ebook template
> and it crashes reliably.
Should say how... there's an existing hyperlink text & link = "http://theWebalyst.com"
Right click on the link, Edit Hyperlink
In the dialog, contents of "Target" are selected: http://theWebalyst.com/
I click after the final '/' to unset the selection and place the cursor after the final '/'
I type '#' to so the content becomes http://theWebalyst.com/#
Before I do anything else, Writer crashes.
Aside: it looks as if just having this dialogue open might be flakey as while I reviewed this description, Writer crashed while just sitting there with the Edit Hyperlink dialog open, before I changed anything.
Thanks for additional information
Sorry for can not reproduce this bug in 3.5.3 on Fedora 64 bit and in 3.5.2 on Windows 7 32 bit
This bug reproducible on another computer?
Created attachment 62630 [details]
Bug 38932 - WinDbg session with FAILED_SOURCE_CODE
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit
Crash while editing hyperlink.
Attached full WinDbg session with FAILED_SOURCE_CODE.
It is the same section of the code as in bug 47044 and many others mentioned there.
this indeed looks like a duplicate of bug 47044
*** This bug has been marked as a duplicate of bug 47044 ***