|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Picture Drag and Drop from WIN Files Explorer incomplete | ||
|---|---|---|---|
| Product: | Calc | Reporter: | Rainer Bielefeld <rainerbielefeld_ooo_qa> |
| Component: | code | Assignee: | AOO issues mailing list <issues> |
| Status: | CONFIRMED --- | QA Contact: | |
| Severity: | Normal | ||
| Priority: | P3 | CC: | openoffice, orw, rainerbielefeld_ooo_qa |
| Version: | 4.1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Windows 7 | ||
| Issue Type: | DEFECT | Latest Confirmation in: | 4.2.0-dev |
| Developer Difficulty: | --- | ||
Test on Win7 HP, 64bit, 8GB RAM, AOO4.1.0 release (Build:9764) Dragged and dropped my complete sample image folder (222 different generated images of ~1800x1200) into an excel sheet. Memory consumption increased to 600MB, then dropped to ~65MB when I zoomed out to see the result. I see four images places in a diagonal fashion below each other, and the navigator also sees exactly four. (But I wonder ... why would a user do this? Or more precisely: What would you expect if you dropped dozens of images onto one position in an excel sheet? A pile of them at the same location? Probably this is only a test scenario, so I should not think too much about it.) So I see your observation CONFIRMED. (In reply to Matthias Basler from comment #1) > (But I wonder ... why would a user do this? Or more precisely: What would > you expect if you dropped dozens of images onto one position in an excel > sheet? A pile of them at the same location? Of course that's not a standard application how to handle pictures. But It's a comfortable way to get a bigger number of pictures into a document, and afterwards you can drag & drop or cut & paste them to the positions where you need them. I did that test to find vulnerabilities concerning picture handling. Can you do the same test with Draw and Writer? @Oliver: May be you want to check dependencies to your other picture loss fix activities? Tested all three components once more with 222 images: - Calc: Memory goes up to 1200 MB this time, then drops to 65 MB. Only 4 images remain. - Writer: crashes when it reaches ~1650 MB memory usage - Draw: crashes when it reaches ~1650 MB memory usage Tested on Win7 HP, 64bit, 8GB RAM, AOO4.1.0 release (Build:9764) |
Steps how to reproduce Reproducible with "AOO 4.2.0-Dev – German UI / German locale [AOO420m1(Build:9800) - Rev. 1597166 2014-05-20 1]" on German WIN7 Home Premium (64bit)", “historic” 4. User Profile used for all predecessor versions: 0. Launch WIN Task Manager 1. From AOO Start Center open blank new Calc document 2. In WIN explorer in a folder select a range of 200 typical private digicam .jpg photos (0,5 ... 3 MB) 3. With control+mouseclick drag and drop pictures to Calc sheet > For a while Calc becomes unresponsive > For a while memoriy consumption increses > but then, while Calc still is not responding, memory will decrease more and more 4. When Calc has become responding again, check Number of Graphics in Navigator: only 4 or so will be in document 11. Compare behavior with server installation of " AOO 4.0.0-Dev – English UI / German locale [AOO400m1(Build:9700) - Rev. 1457992 – Rev.1457606 ((2013-03-19))]" on German WIN7 Home Premium (64bit)", own separate user profile > That one will bravely import hundreds of pictures Because Rev. 1457992 already shows "Issue 124999 - Huge memory consumption for very large and complex .odt" I think this one is independent from that one with memory consumption. @Oliver: May be you want to check dependencies to your other picture loss fix activities? @Matthias Can you confirm my observations?