View Issue Details

IDProjectCategoryView StatusLast Update
0002298FreeCADBugpublic2017-03-02 16:32
Reporterbricechart Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
Platform64-bitOSWindowsOS Version10
Product Version0.15 
Summary0002298: Excessive Memory Use with Skype Screen Sharing
DescriptionWhen FreeCAD is open in the background while using Skype screen sharing, FreeCAD starts using excessive memory. This only happens when FreeCAD is in the background.
Steps To ReproduceOpen FreeCAD and load FCStd file. Initiate Skype call. Share screen (through Skype) from the PC with FreeCAD open and running. Minimize FreeCAD and continue to use screen sharing via Skype. After several minutes FreeCAD's RAM usage will continually increase, eventually creating an out of memory issue on the PC. When FreeCAD is brought back to the foreground or FreeCAD is closed, the memory returns back to normal level.

Problem occurs only when Skype screen sharing. Problem has occurred with Windows 8, Windows 8.1 and now Windows 10. Skype is the latest version (7.10.64.101).
Additional InformationUsing Intel HD graphics, with i7-620M processor and 8GB RAM.
TagsNo tags attached.
FreeCAD Information

Activities

Kunda1

2017-01-13 16:43

administrator   ~0007720

@bricechart Plz retest on 0.16 to see if issue still persists

Kunda1

2017-01-19 15:45

administrator   ~0007883

Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20055

Kunda1

2017-01-25 12:53

administrator   ~0007983

No response from @bricechart
Resolving as 'unable to reproduce'

Issue History

Date Modified Username Field Change
2015-10-14 18:22 bricechart New Issue
2017-01-13 16:43 Kunda1 Note Added: 0007720
2017-01-13 16:43 Kunda1 Status new => feedback
2017-01-19 15:45 Kunda1 Note Added: 0007883
2017-01-25 12:53 Kunda1 Note Added: 0007983
2017-01-25 12:53 Kunda1 Status feedback => resolved
2017-01-25 12:53 Kunda1 Resolution open => unable to reproduce
2017-01-25 12:53 Kunda1 Assigned To => Kunda1
2017-01-25 13:00 Kunda1 Assigned To Kunda1 =>
2017-03-02 16:32 Kunda1 Status resolved => closed