Watch, Follow, &
Connect with Us

QualityCentral

Public Report
Report From: Delphi-BCB/IDE/Packages/Installing Components    [ Add a report in this area ]  
Report #:  102536   Status: Reported
Re-installing used component can crash Delphi
Project:  Delphi Build #:  16.0.4358.45540
Version:    16.3 Submitted By:   Curt Mayers
Report Type:  Crash / Data loss / Total failure Date Reported:  1/11/2012 6:51:20 PM
Severity:    Infrequently encountered problem Last Updated: 1/12/2012 6:11:26 PM
Platform:    All versions Internal Tracking #:  
Resolution: Need More Info (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
This happens frequently but sporadically, but is severe enough in its repercussions to report notwithstanding its dicey repeatibility.

In working on a project that includes custom visual components, if the component source is modified and reinstalled, the installation will often happen correctly, immediately followed by a pointer error.

Then follows a cascade of pointer errors, which leaves the user unable to save his work, or--for that matter--do anything but kill Delphi in the Task Manager, and try to re-construct the work.

Please see screenshots for an actual example.  

I am encountering this error several times per day.
Steps to Reproduce:
These steps are not guaranteed to replicate the error, but they are the steps that will cause the error to happen on my system / project.

1.   Create a project that has a custom visual component, and registers it.
2.   Create another project with a VCL forms project.
3.   Create a project group that contains both.
4.   Place your visual component on the form of the VCL forms project.
5.   Modify the source for the visual component, and recompile it.
      a.  An exception may occur here.
6.  Install the component.
      a.  The exception cascade may start here, as well (more likely).
7.  The IDE is now effectively shut down:   any attempt to access the editing screen,
     or save source (from either project), or even close the IDE is met with access violation
     dialog boxes.   Dismissing them just produces another.
8.  After dismissing several of these dialog boxes, the entire IDE is "disabled" and
     entirely inaccessible.   At this point, the only option is kiling BDE in the task manager .
Workarounds
None
Attachment
102536.zip
Comments

Curt Mayers at 1/11/2012 6:57:26 PM -
Attachment legend:

1.  On this round, the following exception was encountered upon compiling the registration unit for the custom component.   The module that the exception was nominally found in (a third party library) was not part of the changed component.

2.  Following this, I attempted to "Clean" the source for the registration unit, and got this exception.

3.  Finally, I got a cascade of this exception on any attempt to access an editing window, to compile either project, or to save the contents of any file.     I got this exception 4 or 5 times before the IDE was "disabled."

Please note that this sequence is common, but not the norm:   it happens, on average, every 6th or 8th comple round when developoing visual components.   It is not specific to a single visual component (the precise sequence above has happened with different components, contained in different project files),

Tomohiro Takahashi at 1/11/2012 9:54:32 PM -
> Platforms: Win 64 bit
Does your issue occur only on 64bit OS?
and, could you please re-attach sample package project(including screenshots) to confirm your issue?

Curt Mayers at 1/12/2012 3:46:15 PM -
1.   I don't know:  my development machine is 32-bit.
2.   The project I'm working on is quite large (> 200,000 lines), and proprietary.

Tomohiro Takahashi at 1/12/2012 6:09:04 PM -
ok, if possible, could you please contact technical support service for more investigation?
http://support.embarcadero.com/

Curt Mayers at 1/16/2012 2:53:28 PM -
I don't understand:  you want me to visit the web site?

Tomohiro Takahashi at 1/16/2012 7:43:08 PM -
> 2.   The project I'm working on is quite large (> 200,000 lines), and proprietary.
Have you already contacted technical support service or Sales rep of Embarcadero?

Christophe LACH at 1/12/2012 8:10:03 AM -
I have also encoutered this with XE2 32bits
work well if you start a fresh delphi and work on the component package, but not if you were previously in a project form that uses the package. Sometimes I also get back to the deskop (fast) without an error.

I took the habbit of closing delphi and reopening it before working on a component package. by luck Xe2 is fast to close and re-open ;)

Tomohiro Takahashi at 1/12/2012 6:11:18 PM -
Do you have any sample project(s) to reproduce your issue?

Server Response from: ETNACODE01

Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.