# The form data below was edited by perforce # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000555 Status: open Project: perforce-software-p4connect Severity: A ReportedBy: kpark ReportedDate: 2016/07/27 20:45:09 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:35 OwnedBy: kpark Description: When adding more than 1000 files, a crash occurs on Windows 7(x64). Since the customer is a prospect, and currently evaluating Perforce with P4Connect, it would be appreciated if we could fix the problem as soon as possible. Reproduce Steps; 1. Download the customer's project from the following link; https://drive.google.com/file/d/0B3CpP6A8uVmkRHZYUHN5NC1TLWs/view?usp=sharing 2. Go to ~\Assets\"New Folder" in Windows Explorer, and copy & paste *.cs files to make more than 1000 files 3. Open the project in Unity 4. Install P4Connect (2016.2.138.5874-Release) 5. Select all files in Project -> Assets -> "New Folder" in Unity, and right-click on the files, and go to Perforce -> "Add to depot" 6. Crash occurs DevNotes: Type: Bug