Access violation

rbuser

I'm regularly getting these in the report designer; D2005 Enterprise,
RB 10.08, XP SP2. In t his case I un-checked "Parent width" on a line,
sometimes it happens setting the autosize property. Exiting the report
designer and going back in clears it up temporarily.

Any ideas?

date/time : 2008-05-26, 19:18:28, 712ms
computer name : D2005A
user name : Administrator
registered owner : Bespoke Software, Inc.
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 1 day 8 hours
program up time : 4 minutes 38 seconds
processors : 2x Intel(R) Core(TM)2 Quad CPU @ 2.66GHz
physical memory : 83/511 MB (free/total)
free disk space : (C:) 166.79 MB
display mode : 1712x1457, 32 bit
process id : $52c
allocated memory : 30.23 MB
executable : VSys.exe
exec. date/time : 2008-05-26 19:13
version : 1.2.0.2
compiled with : Delphi 2005
madExcept version : 3.0e
callstack crc : $16620274, $eb6b4a11, $20940364
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 009C126B in module
'VSys.exe'. Read of address 00000098.

Main ($210):
009c126b VSys.exe ppDesignSelection 343
TppDesignSelection.Contains
009b6c73 VSys.exe ppPopupMenus 1260
TppComponentPopupMenu.SetPropValue
009b68d2 VSys.exe ppPopupMenus 1103
TppPopupMenu.ToggleBooleanItemValue
009b6797 VSys.exe ppPopupMenus 1016
TppPopupMenu.BooleanItemClick
00816925 VSys.exe ppTB2Item 1468 TppTBCustomItem.Click
00816810 VSys.exe ppTB2Item 1418
TppTBCustomItem.ClickWndProc
00477d7c VSys.exe Classes StdWndProc
77d496c2 user32.dll DispatchMessageA
004cdfb8 VSys.exe Forms
TApplication.ProcessMessage
004cdff2 VSys.exe Forms
TApplication.HandleMessage
004ca5ad VSys.exe Forms TCustomForm.ShowModal
009c805f VSys.exe ppEndUsr 1921 TppDesigner.ShowModal
00ee5d0f VSys.exe baseCustomReportFrames 172
TBaseCustomReportFrame.designReport
00ee59e5 VSys.exe baseCustomReportFrames 116
TBaseCustomReportFrame.onDesignClick
00aab7cf VSys.exe GMSToolPanels 493
TGMSToolPanel.intOnClick
00aa5ce3 VSys.exe ToolPanels 5746 TAdvToolPanel.MouseUp
00aabec4 VSys.exe GMSToolPanels 689 TGMSToolPanel.MouseUp
004ab7ec VSys.exe Controls TControl.DoMouseUp
004ab86e VSys.exe Controls TControl.WMLButtonUp
004ab250 VSys.exe Controls TControl.WndProc
004ae6f2 VSys.exe Controls TWinControl.WndProc
004ae110 VSys.exe Controls
TWinControl.MainWndProc
00477d7c VSys.exe Classes StdWndProc
77d496c2 user32.dll DispatchMessageA
004cdfb8 VSys.exe Forms
TApplication.ProcessMessage
004cdff2 VSys.exe Forms
TApplication.HandleMessage
004ce212 VSys.exe Forms TApplication.Run
013470d9 VSys.exe VSys 1220 initialization

rbuser

Hi William!


I'm also getting access violations on a regular basis. It's always when I
exit a combo box in the property manager on the left.

The workaround for me is to click on the report after selecting the value
from the combo box instead of clicking on the property manager.

Maybe it's the same for you?

Kind regards,
Christoph



--- posted by geoForum on http://delphi.newswhat.com

nicocizik

Hi William,

Are you getting these errors at runtime or designtime (or both)? Are you
able to consistently recreate the error if you follow a certain procedure?
If so, let me know the steps I can take to see this on my machine. So far
with my testing with RB 10.08, D 2005 on my XP machine, I have been unable
to see an error.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

I can only wish for consistency here, it would make the process much
easier! We've only seen it happen at runtime; when it does it's on my
development machine, testing machines and on numerous customer
machines. I don't do anything interesting in my own code when the
designer is up, I pretty much leave it to its own devices, so my code
isn't getting involved.

When it's happened in the debugger, I've been able to trace down that
in ppPopupMenus.pas, around line 1260,
if (SelectionController <> nil) and
(SelectionController.Selection.Contains(GetComponent)) then
SelectionController is not nil, but neither does it point to a valid
object.

rbuser

Is there any help coming on this issue?

nicocizik

Hi William,

Sorry about the delay, my news reader somehow lost track of this post.

I am still unable to recreate the issue here on my machine(s). If possible
please construct a simple test case that I can run here that recreates the
issue and I'll take a look at it for you. Send the example along with steps
on how I can recreate the issue to support@digital-metaphors.com in .zip
format.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

We can't reliably reproduce it here, though it happens regularly on
client machines (it's only once appeared while I was debugging).

Given the stack trace and the problem's context (in ppPopupMenus.pas,
around line 1260, SelectionController is not nil, but neither does it
point to a valid object), it's clear that the designer is losing track
of the selection. Since before the error pops up the designer seems to
be working correctly, my guess is that SelectionController is
properly created but it's erroneously being freed somewhere in your
code before that.

nicocizik

Hi William,

Please understand that if we cannot reproduce the issue here on our
machines, it is nearly impossible for us to track down a probem and provide
a solution. We have taken a look at the code you mention below however have
not been able to see a problem. Perhaps try simplifying your report(s) to
see where the problem, or culprit may lie. Periodically removing report
components, custom classes, or event handler code may reveal the issue.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com