Watch, Follow, &
Connect with Us
Core VCL Classes
DFM to TEXT
Registry / INI Objects
Win 3.1 Controls
Win 32 Controls
You are not logged in.
[ Add a report in this area ]
TOpenPicture does not handle jpg - uses jpeg causes Vista 64 Bluescreen on executing
Crash / Data loss / Total failure
9/29/2009 5:10:07 AM
Infrequently encountered problem
9/15/2012 4:28:17 AM
Internal Tracking #:
Need More Info
Resolved in Build:
Voting and Rating
No Ratings Yet
0.00 out of 5
The StandardAction dialog member for load picture does not include facilities to handle jpg images. If 'jpeg' is added to the 'uses' header then when the program is compiled, built and executed and a jpg image selected it will cause a catastrophic Vista bluescreen and often over-write the project *.dpr file with nulls. If the program is stepped through when executing, the TOpenPictureDialog code will trigger, and the file selection window will be shown. If a file is selected then a message box will flash up stating that the source has been changed and asking if the program should be rebuilt (answering with cancel enables the program to be resumed with F9). It would seem that the 'uses jpeg' statement triggers this action.
Steps to Reproduce:
Use ActionManager, and any ActionBar, group, ribbon etc., and select the OpenPicture Dialog from the standard actions. Add an image control and a few lines of code in the Openexecute section to load a picture into the image control. Add 'jpeg' to the uses section compile build and run --> blue screen too many times to count!
The workaround is to avoid using the TOpenPicture from the standard actions, and build your own TOpenPicture action using the standard components as these read jpg files without needing anything added to the 'uses' header file.
Tomohiro Takahashi at 9/29/2009 11:23:41 PM
Could you please attach sample project to reproduce your issue?
Ed Peach at 9/30/2009 8:34:09 AM
Pleas give information on how a sample project may be uploaded.
Tomohiro Takahashi at 9/30/2009 6:13:18 PM
Please use Windows Native QC client to attach .zip file.
The standalone client comes with Delphi.
Ed Peach at 10/1/2009 4:01:46 AM
Sample project attached (hopefully, as I had a lot of site timeouts when attempting to post).
I noted no crash problems with the standalone exe file, all problems seem to be when compiling, building saving then running within the Delphi environment. If a crash doesn't take place immediately, make a few minor alterations, compile, build, save and run a couple of times. I obtained a crash within two such iterations on three separate attempts.
I do not think there is anything obviously wrong with the attached code, however, even if there is, it should not produce a blue screen but fail gracefully.
Ed Peach at 9/30/2009 8:32:15 AM
Workaround may not always work - crashes still experienced in this section but they are now intermittant in nature (depend on memory usage?)
Seppy Bloom at 9/30/2009 2:54:04 PM
Have you tried this on a 32-bit OS?
Ed Peach at 10/3/2009 12:31:36 AM
I managed to find an old lap-top which would take Windows 7 RC., and installed Delphi 2010 on it as well. When running the test program it threw an "Appcrash report" 50% of the time, and named bsd.exe, ntdll.dll and kernel32.dll in the Microsoft report. About the only improvement was there was no Blue Screen!
<?xml version="1.0" encoding="UTF-16" ?>
<Product>(0x1): Windows 7 Ultimate</Product>
<ParentProcessPath>C:\Program Files\Embarcadero\RAD Studio\7.0\bin\bds.exe</ParentProcessPath>
<ParentProcessCmdLine>"C:\Program Files\Embarcadero\RAD Studio\7.0\bin\bds.exe" -pDelphi</ParentProcessCmdLine>
<SystemProductName>Presario 2100 (DP834E)</SystemProductName>
Looks like a bug which is at least common to the Vista+ OS's.
I've now gone back to using TurboDelphi 2006 for development as that seems much more stable.
Tomohiro Takahashi at 10/4/2009 5:58:24 PM
> ... "Appcrash report" 50% of the time, and named bsd.exe, ntdll.dll and kernel32.dll in the Microsoft report.
We have encountered same error(Appcrash) when running an application with IDE. In the case, the crash is caused by IME of Office 2007.
Ed Peach at 10/1/2009 2:54:58 AM
No - sorry I do not have a Vista 32 bit handy, and the blue screen crashes are far too catastrophic (immediate shutdown) that I do not want to risk messing up disk drives. It is bad enough only on one rig (which by the way has 8Gb of memory - which may itself be an issue, if memory measurements are screwed up in some way).
Tomohiro Takahashi at 10/4/2009 6:00:40 PM
I run the attached application on Vista 64bit Japanese edition. But, no crash, no blue screen.
Ed Peach at 10/22/2009 4:15:11 AM
I see that Microsoft are not recommending that RAD Studio 2010 be installed in Windows7
" Known Issues"
You may experience issues running this program on Windows 7 (true).. Before upgrading we recommend uninstalling this program.
Unlike other programs it says nothing about being able to safely reinstall after ther upgrade.
I suspect this may be why I have experienced issues running Vista 64 bit.
Ed Peach at 10/5/2009 3:57:12 AM
I need to do some more checking, but it appears that ESET Antivirus may be the cause of the problem. I turned off ESET active checking within the Embarcardo directory (e.g. area where bin files reside), and so far I have not activated a crash whereas this was pretty much a guaranteed event. I'll slowly increase testing. I'm reluctant to move full development back just yet as the crashes actually caused disk corruption (due write behind cache).
I'd appreciate your comments on the possible interaction between the ESET security suite and the compiler/linker. I don't particularly like running with an antiviral turned off so I will move development to a sandboxed virtual guest without A/V as soon as Win7 is released.
The Win7 machine also had an anti-virus present and active (Avira free version). Maybe a common problem area as both use proactive rootkit detection etc.
Ed Peach at 10/5/2009 12:42:30 AM
Ugh - I assume that you saw no major errors in the trivial code I sent to you.
In which case it is an environment thing (possibly ESET Antivirus/Firewall?), or memory/page size. However, it does not explain why it also crashed on a freshly installed Win7 machine. (albeit very old and very low in memory).
Did you make a minor change and recompile, save and then run before testing? It was that step which triggered a blue screen, the exe itself runs with no issues.
View Your Reports
Server Response from: ETNACODE01
Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.
3rdRail & TurboRuby
Add Content (GetPublished)
Audio & Video
Bugs & Suggestions (QualityCentral)
Registered User Downloads
Add Content (GetPublished)
Bugs & Suggestions (QualityCentral)