Bug 439779 - [Mac] unexpected shutdown when changing Printsize
Summary: [Mac] unexpected shutdown when changing Printsize
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2014-07-17 06:22 EDT by Matthias Proppe CLA
Modified: 2019-11-27 07:06 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Proppe CLA 2014-07-17 06:22:11 EDT
I wanted to print one file. But I wanted to print it not 100% but 50%. So I put the cursor between the two 0s and wanted to delete 0, 1. But when I deleted the 1 eclipse shut down unexpected. In the 3rd attempt I typed the 5 first (1050%) and deleted then the 0 and the 1. That worked.
So probably the temporary 0% makes eclipse shut down!
Comment 1 Wojciech Sudol CLA 2014-07-17 08:15:00 EDT
What is the version of your Eclipse?
Could you attach a log file (<WORKSPACE>/.metadata/.log) and a screenshot of the "Print" dialog?
Comment 2 Daniel Rolka CLA 2014-07-21 08:15:10 EDT
(In reply to Matthias Proppe from comment #0)
> I wanted to print one file. But I wanted to print it not 100% but 50%. So I
> put the cursor between the two 0s and wanted to delete 0, 1. But when I
> deleted the 1 eclipse shut down unexpected. In the 3rd attempt I typed the 5
> first (1050%) and deleted then the 0 and the 1. That worked.
> So probably the temporary 0% makes eclipse shut down!

Can you confirm that the print dialog works fine for other applications (other editors) when you repeat the same steps that cause the crash of Eclipse?

Daniel
Comment 3 Lars Vogel CLA 2019-11-27 07:06:07 EST
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.