Last modified: 2013-09-07 10:35:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T52465, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50465 - VisualEditor: Cut-and-paste swap of reference list creates massive content duplication, pawns (♙) and snowmen (☃) galore
VisualEditor: Cut-and-paste swap of reference list creates massive content du...
Status: RESOLVED WORKSFORME
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: Normal major
: ---
Assigned To: Ed Sanders
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-30 17:12 UTC by Oliver Keyes
Modified: 2013-09-07 10:35 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Oliver Keyes 2013-06-30 17:12:31 UTC
https://en.wikipedia.org/w/index.php?title=Edamattom&diff=562268939&oldid=562266260 <- this was from an attempt to swap a references section and an external links section. We cannot have this scale corruption on launch. I'd be most grateful if someone could find out what the heck happened, and also confirm with some degree of certainty that it won't happen again.
Comment 1 Jarry1250 2013-06-30 17:16:08 UTC
Given the severity, I'll try to recreate what I was doing but it was basically an attempt to cut the existing External Links section and paste it after the References. As I had made other changes, I can't rule out the idea that I could have stopped editing at the first sight of white pawns; certainly, I saw a couple just before the main "whumpfh" of the loop kicking in, but the loop might have already started by then.

Browser: Chrome latest (27.0.1453.116) running on Windows 7. Plenty of RAM (before the loop, anyway :P).
Comment 2 Jarry1250 2013-06-30 17:17:22 UTC
Oh, meant to add that the loop may well have been infinite but I tried to force the save (with ultimate success).
Comment 3 John Mark Vandenberg 2013-07-22 02:48:35 UTC
I can reproduce it.  With a lot of the pawn bugs fixed now, maybe it has disappeared.
Comment 4 Ed Sanders 2013-09-07 10:35:37 UTC
I think this has been fixed for a while. Re-open if you can reproduce it.

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


Navigation
Links